UK University Attendance: Fix a Missing Check-In

Know Your University’s Check-In Rules

Before the next class, find the attendance section of your module handbook or student portal and record:

• the official app or website and whether SSO/MFA is required;
• the allowed check-in window and what “late” means for this module;
• whether QR, card, iBeacon, browser or a manual register is the approved alternative;
• who can correct a record — lecturer, School Office, faculty administrator, attendance team or IT;
• how long a technical issue or incorrect absence can be reported after the class.

Do not use a flatmate’s phone, ask another student to scan for you, or change your location to make a check-in appear. The record must reflect your own attendance and the method your university has approved.

The official examples below show why local instructions matter. Greenwich says its QR/passcode method can be supplemented by a tap-in card reader where available. Dundee says students with SEAtS problems should use the School Office after each class while the technical issue is resolved. Neither page creates a rule for every university.

What to Do When the App, QR Code or Wi-Fi Fails

Use this sequence during the class:

1. Stay in the session. Note the module, room, date, start time and the time the error appeared. Do not leave just because the first check-in attempt failed.
2. Capture the problem. Take screenshots showing the error, loading screen, QR page, URL and your device time where possible. If the page hides the time, write the time in your notes immediately.
3. Try the approved route once or twice. Check that you are using the correct account, SSO and MFA; restart the app; try the university’s official browser version; or switch from Wi-Fi to mobile data if your policy permits it. Do not install an unofficial workaround or spoof location.
4. Tell the tutor before the class ends. Show the error and ask whether they can use the official manual register or tell you the approved alternative. If the tutor is busy, send a short message through the channel the course uses while you are still in the room.
5. Report the incident. Use the School Office, attendance team or IT helpdesk named in the policy. Include the ticket number in your later correction request.
6. Keep learning evidence. Retain notes or a learning activity from the session, but treat them as supporting context, not a substitute for the university’s register.

The University of Greenwich guidance on incorrect QR attendance warns that attendance normally has to be registered at the time of the register and may not be retrospectively amended, so report the issue while the class details are fresh. Other universities may offer a different correction route.

A short message to send during class

Subject: Attendance check-in problem – [Module] – [Date]

Hello [Tutor / School Office],

I am in [room/building] for [module] today, [date], starting at [time]. I have tried the official [app/QR/card] check-in at [time], but [brief error]. I have attached a screenshot and will remain in the session. Could you please confirm the approved alternative or where I should report this?

Thank you,
[Name and Student ID]

After Class: Check Whether the Record Updates

Some systems do not display a card swipe or app event immediately. Before escalating, check the university’s stated processing window — but do not use “it might sync later” as a reason to postpone reporting a visible error.

UCL’s official RegisterUCL updates page documents several useful points: attendance data may take days to appear, an initial “absent” status can later be corrected, and an incorrect record should be reported with the module code, date, time, location, registration method and supporting evidence. The page also says a faculty or departmental administrator may need lecturer approval to change a status. That is a UCL process, not a universal three-day rule.

When you check the record:

• screenshot the status and the date you checked it;
• compare it with your original error screenshot and ticket;
• submit the correction through the official form or team;
• quote the module, teaching event, room, check-in method and exact times;
• ask for a reference number and keep the reply.

If the record is corrected, save the confirmation. If it is not corrected, ask which formal attendance review or appeal route applies and follow its deadline.

How to Challenge an Incorrect Absence

Treat this as a factual record-correction request, not an argument about whether attendance rules are fair.

Step 1: Build the evidence bundle

Put these in date order:

• attendance status or export;
• module timetable and room;
• app/QR/Wi-Fi screenshots with timestamps;
• IT or School Office ticket;
• message to the tutor made during or immediately after the session;
• contemporaneous notes or a learning activity that identifies the session;
• any official service-outage notice.

Do not create evidence after the fact or ask a classmate to confirm something they did not personally observe.

Step 2: Use the local correction route

Check your handbook for the named recipient and deadline. Start with the lecturer or School Office if that is what the policy says; otherwise use the attendance team or portal. Ask for the exact session to be reviewed, not a general request to “fix my percentage.”

Step 3: Write a concise request

Subject: Request to review attendance record – [Module] – [Date]

Dear [Name / Attendance Team],

I attended [module] in [room] on [date] from [start] to [end]. The record currently shows [absent/late/missing]. I attempted to register using [method] at [time], but [brief factual description]. I reported the problem to [person/team] at [time] and received reference [number].

Attached are [list of evidence]. Please could you review this specific teaching event and confirm whether any further information is required? I understand that the university’s attendance policy and approved records control the decision.

Kind regards,
[Full name and Student ID]

Step 4: Escalate carefully

If the first recipient cannot change the record, ask for the next official route and the deadline. Keep each follow-up short and attach the existing reference number. If an incorrect absence has contributed to a low-attendance warning, link the correction request to the warning and follow both deadlines. The low attendance warning guide explains how to reply to the wider engagement process.

Wi-Fi, QR and App Troubleshooting Checklist

Before each class:

• update the official app and check that SSO/MFA works;
• charge your phone and know the official browser/card/manual alternative;
• open the approved check-in page early without submitting a false or premature check-in;
• keep the School Office and IT helpdesk links bookmarked;
• know how your course defines late attendance.

When something breaks:

• use mobile data only as a normal connectivity fallback, not to fake a campus location;
• record the network name, error text, time and room;
• ask staff for the approved alternative while you are present;
• report the issue even if a later sync fixes the display;
• keep the ticket and final correction decision.

The UCL updates page gives an official example of an app/QR/iBeacon issue and the information administrators need. Greenwich’s card-reader guidance and incorrect-QR guidance give official examples of approved alternatives and the need to register at the time. Follow your own university’s instructions if they differ.

Lateness Is Course-Specific

There is no reliable national rule that “two or three minutes late means absent.” Some systems record late separately, some close a check-in window, and some courses use a paper or verbal register. Labs, placements and professionally regulated courses may have additional safety or accreditation requirements.

Read the module handbook and ask the teaching team before you need the answer. If you arrive late, enter safely, follow the staff instruction and record the reason if it is relevant. Do not attempt a second person’s check-in to make the system show “present.”

Student Visa and Academic Engagement Context

For Student visa holders, attendance can sit inside the university’s academic-engagement and sponsorship process. The Home Office sponsorship duties guidance requires higher-education sponsors to have and apply an academic-engagement policy. The policy can use attendance, contact points, online engagement or other indicators, and the intervention period depends on the relevant band and the university’s rules.

Dundee’s Student visa guide is a useful example of a university explaining its own threshold, support contact, warning and meeting stages. It also warns that deliberate dishonesty in attendance recording is serious. A technical check-in problem should therefore be reported honestly and promptly; it is not permission to bypass the system or a guarantee that an attendance record will be changed.

If an attendance record has already contributed to a formal warning, respond to the warning as well as filing the technical correction. If you receive a sponsorship or withdrawal notice, contact your university’s visa team and obtain regulated immigration advice promptly. No website can promise that a correction will stop a visa action.

Related Guides

• Low Attendance Warning: What to Reply and Do Next
• University Extension: Can You Apply After the Deadline?
• University Extension Evidence Checklist

Official Sources Checked on 29 August 2026

• UK Home Office: Student sponsor guidance – Sponsorship duties — explains academic-engagement and sponsor duties.
• University of Dundee: Attendance and your Student visa — current example of SEAtS technical support, attendance warnings and visa-compliance stages.
• University College London: RegisterUCL updates — official example of app/QR/iBeacon issues, delayed data and correction details.
• University of Greenwich: tap-in card reader and incorrect QR attendance — official examples of an approved alternative and the requirement to register at the time.
• University of Leeds: Unsatisfactory attendance and engagement — official example of how unresolved engagement concerns can progress.

Policies and app instructions change. The module handbook, attendance portal and official team at your own university control the outcome.

FAQ

What should I do if my university attendance app is not working?

Stay in the class, note the module/room/time, screenshot the error, try the university’s approved browser or connectivity fallback, tell the tutor and report the incident through the official School Office, attendance or IT route. Save the ticket and check the record later.

What if the QR code will not scan?

Check the official SSO/MFA account and the instructions for your device. Ask the tutor for the approved alternative, such as a card reader or manual register where the university provides one. Do not ask another student to scan for you or use an unofficial workaround.

How do I fix an absence that was recorded by mistake?

Check your policy’s correction window, gather the attendance record, timetable, time-stamped error screenshots, IT/tutor messages and any ticket number, then submit a concise request for the specific module and session. Keep the reference number and escalate through the formal route if the first team cannot amend it.

Can a Wi-Fi or app failure affect my Student visa?

It can become relevant if it leaves an unexplained absence in the university’s engagement record, but a technical failure is not automatically a visa breach or an automatic correction. Report it promptly with evidence and follow the university’s process. Visa outcomes depend on the university’s policy and the relevant immigration authorities.

Is attendance policy the same at every UK university?

No. Systems, check-in windows, thresholds, correction deadlines and sponsor procedures vary by institution, programme and assessment. Use examples from other universities only as questions to ask your own School Office, not as rules to rely on.