Foreign contractor access to Checkinatwork: know what a Limosa QR can and cannot do

A foreign contractor may scan a Limosa document QR code to register presence, but that does not grant every Checkinatwork management capability. Treating the QR as a complete access credential can leave the team unable to review, cancel or resolve an incorrect registration.

Start with the current official rule

The official Checkinatwork guidance for participants describes the route for foreign contractors and the separate process for secure portal access. Confirm who must be registered, which workplace applies and which functions are available through the mobile flow. Do not copy identity documents into an informal chat group to compensate for missing access.

Turn the rule into a bounded decision

Before mobilisation, assign the company and person responsible for registration, review and exceptions. Confirm that the Limosa record belongs to the correct worker and site. If an error appears, use the supported correction or assistance route. A successful QR scan is one event, not proof that every underlying declaration is correct.

Build an auditable workflow

Test access before the first shift. Keep the official reference, time and outcome with the site record. Give supervisors a clear escalation contact when secure access is unavailable. Recheck when a worker, subcontractor or location changes, and avoid sharing portal credentials between companies.

Handle exceptions explicitly

Test the workflow with a realistic exception: a missing company identifier, duplicate record, unclear role or temporarily unavailable source. The process should stop with a focused question. Keep the source, review date, owner and decision without copying more personal data than needed. Escalate legal, tax, labour or safety uncertainty to the competent person.

Repeat the check when a payment, party, invoice action, site arrangement or official instruction changes. An earlier result is context, not automatic permission for the next action. Define who can reverse an error, notify affected people and decide that the exception is genuinely closed.

Make the status readable to someone who did not prepare the record. That person should find the checked input, consulted source, remaining uncertainty and next permitted action. Avoid relying on a free-text note as the only evidence. Use stable fields for identity, date, outcome and owner, then add only the explanation needed for the exception.

Connect context to controlled execution

Enfin can connect the customer, supplier, project, document, task and invoice in one record. Alfie can prepare information and propose a governed action within available permissions; the official service and competent owner remain responsible for the decision. Explore Enfin, review pricing, or discuss your workflow.