Vectis Run · the operating layer for hotel work
Every routine, check and guest issue becomes a task with an owner, a due time, photo proof where it matters and a verification decision — so owners and GMs see exceptions, not noise.
How it works
A ticked box tells you someone pressed a button. Vectis keeps the whole chain — who owned the work, when it happened, what the photo showed, which standard it was checked against, and who decided.
01
One owner, one due time, every task.
02
Staff start and finish on their phone.
03
A photo where it matters.
04
By a manager, or AI against your standard.
05
Exceptions surface. Everything is on record.
Here is one day of it. Sample Hotel, eighteen hours, read like a ledger. The clock and the counters follow you down the page.
In Vectis
Each department's routines live as recurring templates with a schedule, a due time and an SLA. Every morning the day's work is generated automatically — nobody re-types yesterday's checklist. Anything unplanned becomes a quick task in seconds.
Any department's routine can run this way: front office, kitchen, F&B service, housekeeping checks, maintenance rounds, accounts, GM duties.
In Vectis
Every task belongs to one person, and can be reassigned when shifts change. Access follows the role: Owner, GM, Department head, Supervisor, Staff — each sees what their job needs.
Arjun M. · Kitchen
Do this next
Kitchen opening checks
Due 7:00 AM · photo required
Also needs you
Cold room temperature log
Due 8:00 AM
Staff work from My tasks on any phone — an installable web app, no app store. Do this next, Also needs you, Start, Take photo, Retake, Redo. Almost no typing.
Awaiting verification
In Vectis
Photo proof is required on the tasks that matter. Each one is checked against a verification protocol — the hotel's written standard, broken into criteria and versioned. A task keeps the exact version it was created under, so yesterday's decision is never judged by today's rules.
Verification protocol · v3 · 4 criteria
Writing the standard is helped too: in Verification Studio, AI suggests checks for a standard, and a manager writes, edits and publishes them.
In Vectis
When a task runs past its due time it is marked overdue, then escalated — a status the supervisor sees on the Overview, with Needs attention now at the top. The language stays plain: “Overdue since 9:00 AM”, never “you failed”.
Earlier unresolved work is shown separately as backlog. It is never quietly hidden.
Sample Hotel · 09:05
Escalated or missed
1
Overdue (SLA)
1
Awaiting verification
3
In progress / pending
12
Needs attention now
Lobby & corridor cleaning
Rahul D. · Overdue since 9:00 AM
Earlier unresolved
None from yesterday · shown separately when present
In Vectis
Guest complaints run through the same loop as everything else: an owner, a deadline, proof and a verification decision. Nothing lives in a chat thread that scrolls away.
In Vectis
Every hour, rule-based checks read the records themselves and raise signals when something looks unusual. A person reviews the context and decides. Most signals have an ordinary explanation — the point is that someone looked.
Work failure
3 · AI assessment
Result: Work failure · Sent to a person
17:06 · Neha K. requested rework. Recorded as a human decision, separate from AI.
In Vectis
Criterion by criterion, with its reasoning shown to the reviewer. Every result lands in one of four outcomes:
Meets the standard. Ready to verify.
The work is wrong. Goes back for rework.
The photo can't prove it. A new photo is needed.
Always goes to a person. Never automated.
Pass
4 · History
In Vectis
Rework means the work was wrong. Retake means the photo can't prove it — “this is about the photo, not the work.” Vectis counts them separately, so a blurry photo never reads as bad work.
Evidence inadequate
Every state change is timestamped and logged in an append-only audit trail. Every AI result keeps its photo, protocol version, model and reasoning.
In Vectis
Feedback forms for stays, dining and events. Staff open the form on their phone and hand the device to the guest; a photo can be taken on the spot. Ratings are visible to managers alongside the day's operating record.
Sample Hotel · Restaurant · Table 6
Overall
4 of 5
Comment
“Lovely food and a calm room. Dessert took a while.”
Photo
Optional · taken on the spot
63
Tasks
61
Done
24
Verified
4
Exceptions
2 not done → carried into tomorrow as earlier unresolved backlog, shown separately. Exceptions: 1 escalation, 1 complaint, 1 integrity signal, 1 rework — each with its own record.
In Vectis
The Daily Operations Report breaks the day down by property, department and person — print it, save it as PDF or export CSV. Owners and GMs also get an in-app daily briefing.
Built for groups from day one: switch between properties, with every record and every role scoped to its property.
Sample Hotel · by department
| Department | Done | Verified | Exc. |
|---|---|---|---|
| Front office | 14/14 | 6 | 1 |
| Kitchen | 12/12 | 4 | 0 |
| F&B service | 11/12 | 6 | 1 |
| Housekeeping | 13/14 | 5 | 1 |
| Maintenance | 7/7 | 2 | 1 |
| GM duties | 4/4 | 1 | 0 |
| Total | 61/63 | 24 | 4 |
Print · PDF · CSV
In Vectis
Every morning at a set time, a PDF of the previous day's operations is delivered to owners and managers on WhatsApp — a daily report, not a stream of pings. It has been running every day at a working hotel since September 2026.
The owner reads the exceptions over coffee. The detail is one tap away, in the report and in the app.
Sample data · WhatsApp
Daily Operations Report — Sample Hotel
4 pages · PDF
Good morning. Yesterday at Sample Hotel: 61 of 63 tasks done, 24 verified, 4 exceptions.
08:00The day, as a list
Skipped the story? Here is all of it. Vectis Run is the operating layer for a hotel's daily work — in daily use at a working hotel since July 2026.
01
Recurring templates per department — daily to yearly, with due times and SLAs — plus quick tasks.
02
Every task assigned to a person. Roles: Owner, GM, Department head, Supervisor, Staff.
03
An installable web app on any phone. Do this next, Take photo, Retake, Redo. Needs a connection.
04
Your written standard as versioned criteria. Each task keeps the version it was created under.
05
Three human decisions. Rework (the work) and retake (the photo) are tracked separately.
06
Criterion by criterion: Pass, Work failure, Evidence inadequate, Uncertain. Reasoning shown.
07
Per protocol, decide or recommend. Uncertain always goes to a person. Stop switches, audits, AI Quality page.
08
Escalated or missed, overdue, awaiting verification, in progress. Earlier backlog shown, never hidden.
09
Hourly, rule-based signals on the records. A signal is not a conclusion.
10
Daily Operations Report by property, department and person. Print, PDF, CSV, plus a daily briefing.
11
Complaints tracked as tasks with an owner and deadline. Feedback forms handed to guests on a staff phone.
12
Switch between properties, roles per property. Works alongside your PMS — no rip-and-replace.
Why it's different
Plenty of tools can tick a box, and several now put AI on a photo. What matters is what happens around the decision — who is allowed to make it, what happens when it is unsure, and whether a wrong call is caught.
| A checklist records | Vectis records |
|---|---|
| That a box was ticked | Who owned it, when, and the photo that proves it |
| Pass or fail | Four outcomes — and Uncertain always goes to a person |
| “Redo” | Rework (the work) and retake (the photo), counted apart |
| Whatever the AI said | What the owner allowed AI to decide, protocol by protocol |
| The final state | Every change, append-only — including corrected AI calls |
| Nothing unusual | Integrity signals for a person to review |
Where it runs today
We would rather show you less and have all of it be true. Numbers below wait for approval before publication.
Case study · Galaxy
4.5 → 4.9
Galaxy's reported average guest rating rose from 4.5 to 4.9 following its Vectis rollout.
Reported figure. Platform, periods and review counts not yet verified.
Vectis products
The operating layer for a hotel's daily work. Assigned, done, proven, verified, visible.
Turning that operating truth into better guest outcomes and revenue. Not available yet; no dates announced.
Questions
No. Vectis Run works alongside your PMS — it runs the operational work around your rooms and guests. There is no rip-and-replace.
Only where you allow it. Protocol by protocol, the owner chooses whether AI applies its result automatically or recommends to a manager. Anything not authorised waits for a person, Uncertain always goes to a person, and stop switches turn automation off in one click. Corrections are recorded on the AI Quality page.
That is a retake, not a rework. The reviewer — or the AI, as Evidence inadequate — asks for a new photo. It is counted separately from rework, so a bad photo is not recorded as bad work.
No app store. Vectis Run is an installable web app that works on any phone. It needs a connection to save work.
It reads the task records — timings, who completed what, overrides — and raises signals for a manager to review. A signal is not a conclusion; most have an ordinary explanation.
Any department with a routine: front office, kitchen, F&B service, housekeeping checks, maintenance rounds, accounts and GM duties.
Yes. Vectis is built for groups from day one: switch between properties, with records and roles scoped to each property.
The next product on our roadmap — guest feedback intelligence, enquiry and banquet capture, owner intelligence and revenue insight. It is not available yet.
Book a demo
We will walk through Vectis Run using routines like yours — from the first generated task to the morning report.