An Airtable contractor assignment workflow can keep an offered job, the contractor’s response and the coordinator’s final confirmation separate. miniExtensions provides a place to review a specific invitation and respond. Airtable retains which version of the date, location and brief the contractor actually accepted.

Consider fictional Northline Events arranging an adult freelance photographer for a trade-show booth. Morgan is generally available on Thursday, but that does not mean Morgan has accepted a 07:00 arrival at the east entrance. This workflow focuses on that job-specific handoff and on what happens when the invitation changes, rather than just collecting availability.

Model offers as versions, not a changing calendar note

Create Contractors with Name as primary text and Email as email. Jobs has Job reference as text, Brief as long text, Location as text and Planned start and end as dates with time. Availability has Contractor as a link, Start and End as dates with time, Availability note as long text and State as a single select.

Offers has Offer reference as text, Contractor and Job as links, Revision as a number, Offered start and end as dates with time, Offered location and Brief snapshot as long text, Contractor response as a single select, Response note as long text, and Coordinator state as a single select. Add Supersedes as a link to Offers, Confirmed on as a date and Coordinator explanation as long text.

The offer contains a snapshot of the important details, not only lookups that silently change when the Job changes. Use a visible time-zone label in the offer and agree how date/time fields display. Staff owns job details, snapshots, revisions and confirmation fields. Contractors supply their response and any operational question.

Create one invitation for one person and job

The coordinator checks current availability and prepares offer NL-24-R1 for Morgan. The brief describes the expected photography coverage, arrival point and the proposed time window. If payment or contractual terms require agreement, handle those through the appropriate contract process; this article describes operational scheduling, not contract execution.

Build a Portal using Offers as its Data Table and Contractor as its User Field, following the Users table guide. Enable an appropriate verified login through the login documentation. Apply the personal-record setting to each private view so the person sees the intended invitations.

Show Offered start, Offered end, Offered location, Revision and Brief snapshot as context. Keep Job, Contractor and Supersedes out of editable inputs. Suggested responses are Can accept this schedule, Cannot accept and Question before accepting. Explain that the coordinator will separately confirm the assignment after reviewing the response.

Treat a response as evidence for a scheduling decision

Morgan chooses Can accept this schedule and asks where equipment may be unloaded. The coordinator answers the operational question and checks whether the job is still unfilled. Only then do they mark Coordinator state Confirmed and communicate that confirmation through the team’s normal channel.

If invitations are sent to multiple people for one opening, a positive response must not automatically assign all of them. Staff checks the current job before confirming one offer and records the outcome for the others. This schema does not provide atomic booking, conflict prevention or a first-response-wins reservation mechanism.

Likewise, availability ending at noon does not establish enough travel time for a different job starting at noon elsewhere. The coordinator reviews practical constraints and any relevant qualification checks through the organization’s normal process. Do not collect sensitive screening data or make eligibility decisions in this ordinary availability example.

Ask again when the actual offer changes

Suppose the event organizer moves arrival from 07:00 to 06:00 and changes the entrance. Preserve R1 and create R2 with the new details, linking Supersedes to R1. Set R1’s coordinator state to Superseded with an explanation rather than overwriting the terms Morgan answered.

The contractor responds to R2. A prior positive answer remains evidence about R1 only. If Morgan cannot make 06:00, the coordinator arranges another person or revises the job. The portal should not display the original acceptance beside updated times and imply that the change was agreed.

When a cancellation occurs after confirmation, preserve the confirmed record and add the cancellation outcome and explanation. Any cancellation fee, contractual notice or payment decision is handled separately. Recording a cancellation date in Airtable does not send a message or update an external calendar.

Separate actionable offers from history

Use separate views for Awaiting response, Coordinator review, Confirmed and History. Restrict historical editing according to the view-level editing guide and review alternate views, creation and unlinking controls. A contractor must not be able to alter a superseded offer through another route.

If you also display Availability, connect it directly to Contractors and keep it clearly labeled as general availability, not a booking. A change in that table should prompt human review of confirmed work, not automatically cancel or rewrite assignments. Notifications and calendar synchronization need their own configured and tested process.

Run a revision-focused acceptance check

Try two contractors, one job with competing invitations and a confirmed offer that changes time. Verify which revision each response belongs to, who can confirm the job and what the contractor sees after a change. Reload records in Airtable and check that R1 survives intact when R2 is created.

These are recommended checks, not runtime test results. For a broader pool of dates and role preferences, the availability-by-location guide covers that earlier stage. This approach fits small teams coordinating explicit job offers and revisions. Use a scheduling or workforce system when you need reliable automatic conflict detection, payroll or larger-scale dispatch. The practical result here is a clearer answer to ‘Which schedule did this person actually agree to?’