An Airtable training request workflow can collect a course proposal, record a manager’s decision and follow up on attendance afterward. Use a miniExtensions Portal for individual request history, with staff-controlled approval fields and a separate step for purchasing or reimbursing the course.

The fictional Cedar Studio team wants to request ordinary professional-development courses. An employee proposes a spreadsheet workshop, explains the job-related goal and estimates the cost. This example is not a system for regulated training certification, employee assessment or automatic spending approval.

This complements attendance correction requests, which address an existing session record. A training proposal asks for a decision before booking, then gathers follow-up after the activity.

Separate the learning need from the purchase

A course name and price do not explain why the training is useful now. Ask for a practical learning goal: “Build a reusable monthly project-cost report” is clearer than “Improve skills.” Capture the proposed dates and the work handover required, without requesting private personal information.

Approval should describe what was approved. A manager may support the goal but ask for a different date or provider. Record the original request and the approved arrangement separately so a later booking does not make the employee’s proposal appear to have been different.

The outcome is a transparent request-to-follow-up trail. It is not enough to mark a request Approved and assume a booking, payment, calendar hold or attendance record appeared elsewhere.

Model requests and completion evidence

  • Employees: Name as primary text, Work email as email, Team as single select and Manager name as text.
  • Training requests: Request reference as primary text; Employee as a link; Course title as text; Provider website as URL; Learning goal as long text; Proposed start and end as dates; Estimated course cost as currency; Currency code as text; Other expected costs as long text; Handover plan as long text; Request state as single select.
  • Staff decision fields: Decision by as text, Decision date as date, Decision explanation as long text, Approved course and Approved scope as text, Approved start and Approved end as dates, Approved cost ceiling as currency, Booking reference as text.
  • Follow-ups: Follow-up reference as primary text; Training request and Employee as links; Attendance date as date; Attendance evidence as attachment; Practical takeaway and Next application as long text; Staff review state as single select.

One request represents one proposed training activity. Keep multiple courses separate when they need different decisions. For the first version, ask for one currency per request and have staff evaluate total costs. A currency-formatted field does not convert exchange rates or establish what the organization owes.

Keep staff decisions and employee evidence distinct. A submitted certificate is evidence to review, not automatic proof of competence or compliance. Limit evidence to the material needed for the organization’s ordinary process.

Configure the employee-facing request history

Use the request’s Employee link as the user relationship, following the Users Table guide. Follow-ups need their own direct employee link. Do not rely only on their link to a training request.

Use authenticated access and set Personal records only for each employee-facing view. Keep manager decisions outside employee editing. A manager-facing extension would require its own scope and tests; staff can begin with review directly in Airtable.

Give submitted requests a history view and allow changes through a deliberate correction process. The editing restriction documentation applies per view, so check alternative views and linked-record expansion before relying on the restriction. Hiding a decision from a card is not a substitute for checking the editing form.

Review the proposal and record the decision

Alex proposes a two-day reporting workshop costing a fictional 240 in the team’s chosen currency. The manager checks the learning goal, workload, provider details and the relevant budget through the organization’s established process. They approve the workshop but ask for the later session date.

Staff records the approved date and scope in the decision fields while preserving Alex’s original dates. The employee-facing explanation says what happens next: for example, operations will confirm the booking. Only add a booking reference after a real booking exists.

If more information is needed, name the missing fact rather than returning a generic rejection. “Which report will you improve, and who will cover the Friday client meeting?” gives Alex a useful response path. The manager still owns the decision; the portal does not assess merit or entitlement.

Close the loop after the activity

After the workshop, Alex adds a Follow-ups record with the attendance date and a practical takeaway. The next application might be “Draft the March reporting template and review it with the team.” This connects training to planned work without claiming that learning outcomes have been measured.

Staff checks the evidence and records whether the administrative follow-up is complete. Keep reimbursement outside this example. Approval for a course does not prove a payment was made or that expenses meet reimbursement requirements.

For cancellation, retain the request and explain the operational next step. If the course is replaced, create a new request or a clearly linked amendment. Do not silently replace the approved course title while retaining the old approval date.

Verify access, costs and handoffs

Test with two fictional employees and a manager reviewer. Include a declined request, a different approved date, a canceled course, missing attendance evidence and a follow-up linked to the wrong request. Verify that employees cannot select another person’s request or alter staff decisions through any exposed route.

Check how blank costs and multiple currencies are displayed. Avoid a misleading zero when the real meaning is Not yet quoted. Confirm that the request’s status remains distinct from booking and attendance, and that any reminders are separately configured rather than assumed.

These are recommended launch checks, not observed tests. Compared with a general time-off workflow, training needs a learning goal, cost context and later evidence. The model suits a modest professional-development queue; dedicated learning or HR systems may be more appropriate for examinations, mandatory certification, complex budgets or sensitive personnel records.