A student needs a lesson record or help arranging a next step. The office needs to follow the request through. Give work outside the lesson calendar a clear owner, a working-hour deadline, and a place where students can see their progress.
Lesson record requestExample administrative service
Owner
Office coordinator
Work status
In progress
Student sees
In progress
Lesson calendar stays available
Illustrative workflow
Every request has a next step.
Follow an example lesson-record request from the student’s account to the office queue. The school has configured this administrative service with a four-business-hour deadline and a customer-visible status. The lesson calendar keeps its teaching capacity throughout.
A request arrives with its student attached.
A student selects an enabled administrative service, or an authorized member of staff enters it through the school’s order flow. The request belongs to the same customer and order records the office already uses. There is no lesson time to pick: the work goes into the administrative queue, with its assignee and priority visible.
Request
Lesson record · example
Office status
Pending approval
Student view
Received
The request is recorded. Its deadline starts when the office approves it.
The deadline follows your working day.
Approval starts the configured clock. In this example, the office approves the request at 3 pm on Friday and works Monday to Friday, 9 am to 5 pm. Two working hours remain on Friday; the other two fall on Monday. With no holidays, a four-business-hour deadline is Monday at 11 am.
Approved
Friday · 3 pm
Deadline policy
4 business hours
Office due time
Monday · 11 am
Staff see the due time. The student’s request remains Received until its progress changes.
Keep ownership clear as the work moves.
The assignee moves the request into progress. The office can filter its queue by owner, priority, status, or deadline to see what needs attention. If something is missing, staff can mark the work Blocked; the student sees Needs attention. A deadline change requires a reason, keeping the handoff understandable to the next person.
Assignee
Office coordinator
Priority
Normal
Student view
In progress
Everyone sees the relevant progress, while internal timing and activity stay with the office.
Close the request with a visible outcome.
When the administrative work is finished, authorized staff complete the task. The student’s status becomes Completed, with a reference and last-updated time. The office retains the activity history. If the work needs another pass, staff can reopen it under the service’s policy for keeping or restarting the deadline.
Office status
Completed
Student view
Completed
Lesson capacity
Unchanged
The example request is complete. Administrative work has not been counted as a driving lesson.
Illustrative example. Explore each step to see how the workflow connects. This demonstration does not change any school records.
One workflow. A clearer day for everyone.
For students
A Tasks area brings visible requests together in their account. Students can check whether a request is received, in progress, needs attention, or completed, using a clear reference. Where the school allows it, they can withdraw an unfinished request.
For the office
A dedicated queue puts the customer, responsible person, priority, location, and due time together. Move from the queue into the request, follow its history, and use overdue or due-today views to organize the work that needs attention.
For instructors
Administrative work stays separate from bookable lesson time. Where an instructor has the appropriate task permissions and assignment, they can follow their part of the work without turning an office request into a calendar appointment.
Built around your school’s rules.
01
Deadlines shaped around your school.
Choose business minutes, hours, or days against school, location, or assignee working hours. Holidays and custom working days affect the calculation. Use elapsed time when that better fits the service, or leave it without a deadline. The original policy and calendar are retained with the task.
02
The right detail for each person.
Choose whether a service’s requests stay internal, appear as read-only progress, or allow student withdrawal. The student view shows status, reference, and last update. Assignee details, office deadlines, and internal activity remain in the staff workspace, with access controlled by staff permissions.
03
Connected records, clear responsibilities.
Task services keep the school’s customer and order context, including the native financial record where applicable. Their work does not reserve a lesson slot or count toward a student’s training requirements. Staff can trace progress changes, reassignment, and deadline adjustments through the task’s activity history.
A few useful details.
Which administrative requests can we offer?
Your school chooses and enables the administrative services it offers, such as a lesson-record request. Once configured, those requests can be tracked through completion. The example illustrates request handling; it does not automatically create certificates or submit documents to an authority.
Does a task take a space in the lesson calendar?
Administrative tasks have their own queue and do not reserve an appointment date or time. They do not create ordinary Google Calendar lesson events or contribute training credit to a student’s journey. A task is handled as its own order item, separately from lesson purchases.
Can a student see the office deadline?
The customer view gives students the request’s progress, reference, and last update. The working-hour deadline is an office planning detail. Your school also decides whether requests are visible and whether an unfinished request can be withdrawn; withdrawal does not automatically issue a refund.
What happens when a request needs more work?
Staff can mark it Blocked, reassign it, or adjust the deadline with a recorded reason. Completed requests can be reopened according to the service’s deadline policy. Marking a request Blocked does not itself pause its deadline.
Let’s look at your school
Bring your school’s office work together.
Tell us how your office handles administrative requests today. We’ll explore clear ownership, working-hour deadlines and progress updates for your school.
01Tell us about your school
02Choose a time on Calendly
03Walk through your office workflow
✓
Request saved
Now, find a time that works for you.
Your walkthrough request has been saved. Choose a time on Calendly to complete your meeting booking.
Calendly opens on its own website and asks for the information needed to book. Your meeting is confirmed only after you complete that step. Calendly provides the time, confirmation and rescheduling details.
Essential cookies keep RouteOS working. Accept to allow Google Analytics cookies.
Cookie Settings
Choose what you allow
Essential technology works immediately. Optional categories stay off unless you turn them on and save. You can return here at any time to withdraw consent.
Required for security, consent storage, authentication, and core website operation.
Always on
Strictly necessary details
Provider
RouteOS and its website infrastructure providers.
Technology
First-party security, session, authentication, CSRF, load-balancing, and routeos_consent_v1 cookies.
Duration
Session-dependent; the consent record lasts up to six months.
Data and transfers
Security/session identifiers and your non-identifying consent choice. Operational data may be processed in the United States where RouteOS providers operate.
Withdrawal
These technologies cannot be disabled through Cookie Settings because the site needs them to operate securely. The consent record can also be cleared in your browser.
Analytics details
Purpose
Measure page use and site performance so RouteOS can improve the public website.
Provider and recipient
Google LLC (Google Analytics 4).
Technology
First-party _ga and _ga_* cookies; analytics data is sent to Google as a third-party service provider.
Duration
Up to two years, subject to RouteOS Google Analytics retention settings and browser controls.
Data collected
Page path without query parameters, device/browser details, referral source without query parameters, interactions, and approximate location derived by Google. RouteOS does not intentionally send form values or direct identifiers.
International transfers
Google may process analytics data in the United States and other countries where it operates.
Withdrawal
Turn Analytics off here and save. RouteOS updates consent immediately and removes accessible first-party Google Analytics cookies.
Functional
No optional functional vendor or technology is currently enabled.
Not used
Functional details
There is currently no functional vendor, cookie, recipient, duration, collected data, or international transfer to disclose. This category remains off. Adding a functional service requires an updated inventory and a new consent prompt.