Smart Lock Pilot Projects in the United Arab Emirates: How to Scope a First Building
This piece treats uae smart lock pilot scope as a decision document rather than a summary, and each section below carries one piece of the evidence. A first building in the UAE is where a smart-lock programme stops being a catalogue exercise and turns into an evidence exercise. The lock catalogue is settled in an afternoon; what takes months is finding out that the aluminium profile in the service corridor needs a different lock class from the one quoted for guest rooms, that the front-desk team re-encodes cards at a different hour in Ramadan than in January, and that the approval chain will not sign a door assembly it has not seen physically mounted. Each of those findings is cheap to discover inside a pilot and expensive to discover inside a rollout.
Direct answer. A uae smart lock pilot scope is a written definition of what one building is allowed to prove, which door classes it must cover, which evidence must exist before the pilot may have a verdict, and which artefacts survive into the next phase. It is built in seven steps: name the decision, build the door population, fix the credential model, assemble the conformity evidence, prove the environment, run the approval chain, and lock the documentation and training deliverables. The pilot is not a discount-sized order. It is an instrument, and the scope card is how you set what the instrument measures.
On uae smart lock pilot scope, this article uses uae smart lock pilot scope as the definition. It treats uae smart lock pilot scope as a working definition specific to this market and product, rather than a general one.
- Scope first — write down what uae smart lock pilot scope has to settle in the united arab emirates before any hardware is ordered
- Evidence second — attach the document behind each claim in moiat-ecas, not a summary of it
- Owner third — record who signs uae smart lock pilot scope and who keeps the record afterwards
- uae smart lock pilot scope runs this sequence, and moiat ecas is the record it produces.
This guide is written for the system integrator asked "how many locks should the pilot have" and who must answer in a way a consultant, an operator and a contractor can all sign. It works for a serviced residence, a hotel wing, or a mixed-use tower where the hotel is one tenancy among several. The same structure applies to any first building elsewhere; what differs in the UAE are the conformity architecture the buyer meets, the door population the buildings have, and the operating rhythm a hospitality property runs on.
What a Pilot Has to Prove, and What It Must Not Be Asked to Prove
The commonest way a pilot fails is not a bad lock. It is a pilot that was never scoped, so it drifts into proving things it was never designed to prove — usually total cost, brand suitability and rollout timeline — and ends up failing on all three while the real open questions go unanswered.
A pilot earns its place by resolving a short list of uncertainties that are expensive to resolve later and cheap to resolve now. In a UAE hospitality or serviced-residence building that list is stable enough to write down in advance.
| Uncertainty a pilot can resolve cheaply | Why it is expensive later | Evidence the pilot must produce |
|---|---|---|
| Does the lock fit the actual door population | Every unverified door becomes a site variation and a re-order | Door survey sheet with measured fields per door class |
| Does the credential model match front-desk and housekeeping practice | A rejected credential model is a lock change, not a software change | Credential matrix and a dry-run record at the desk |
| Which authority signs off on the door assembly | A late approval failure stalls handover at the worst point | Written confirmation from the named approving party |
| What document set travels with the product | A missing document blocks clearance or the submittal | The moiat-ecas evidence file, per SKU, with issue dates |
| How the hardware behaves in heat, dust and low-maintenance conditions | Field failures arrive after the pilot building has become the reference | Environment test log with the conditions recorded |
| Whether the installer base can commission and maintain it | Training debt is paid in service calls for years | Training record and a commissioning checklist |
Against that list, four things belong on the out-of-scope line of the scope card, because they are what pilots get dragged into: unit economics across the portfolio, brand selection for the group, final network architecture and a rollout schedule. All four are phase-two decisions one pilot building cannot honestly settle, and naming them stops the pilot becoming an excuse for a decision nobody has made.
flowchart TD
A[Scope card signed] --> B[Door population surveyed]
B --> C[Sample bench evidence filed]
C --> D[Mock-up approved on a live door]
D --> E{Pilot verdict}
E -->|Extend| F[Phase two rollout specification]
E -->|Rework| G[Re-open the failing dimension]
G --> B
E -->|Stop| H[Change product class or supplier]
The Scope Card: One Page That Governs the Whole Pilot
Everything else in this guide hangs off a single artefact. Before any lock is sampled, buyer, integrator and operator agree one page stating what the pilot is for, what it covers, what it excludes, and what happens to each answer afterwards. Different organisations call it a pilot scope note, a pilot order summary or a trial agreement, but the content is stable.
CONFIRM-WITH-LOCAL-LEGAL-ADVISER — who signs the pilot agreement, in which capacity, and which party carries the obligation to deliver the documented evidence this scope card calls for.
The scope card carries six fields, each written in the past tense of a decision rather than the conditional, because a scope card made of conditions cannot be signed.
| Field | What belongs in it | Failure if left vague |
|---|---|---|
| Decision under test | The single procurement question this pilot answers | The pilot quietly becomes a general trial and never concludes |
| Covered door classes | Named door classes with measured counts and a sampling rule per class | Fit problems stay hidden until rollout |
| Exclusions | Named door classes, volumes and systems explicitly out of scope | Nobody ever agrees the pilot finished |
| Evidence set | The document and test artefacts that must exist for a verdict | The verdict becomes an opinion |
| Acceptance rule | Who signs the verdict and against which threshold | The pilot ends without a decision |
| Carry-forward | Which artefacts move to phase two, and where they are filed | The pilot's learning evaporates at handover |
The acceptance rule is the field most often left blank, and it is the one that matters. Write it as a named person, a named threshold and a named date. "Technical manager is satisfied" is not an acceptance rule. "The consultant's door-hardware reviewer signs the mock-up record, with zero unmapped door classes and every approval response logged, before the pilot verdict date" is.
Keep the card to one page. If it does not fit, the pilot is carrying too many questions; cut a door class rather than let the card grow into a specification.
Step One — Name the Decision the Pilot Exists to Settle
Most pilots are commissioned with a vague purpose — "try the smart locks" — then judged against a vague result. The integrator's first job is to convert that into a decision somebody has authority to make and a pilot can actually answer.
In UAE hospitality and serviced-residence work, the decisions a first building is usually asked to inform fall into four families, and naming the family matters because each demands a different pilot design.
| Decision family | Typical form of the question | What the pilot must produce | What the pilot must not try to settle |
|---|---|---|---|
| Product class fit | Which lock class suits the door population and the operating model | Measured fit envelope across the named door classes | Which of several brands wins — that is a separate evaluation |
| Credential model | Which credential mix the front desk, housekeeping and residents can run | A working credential matrix with a desk dry run | Group-wide identity strategy or national credential policy |
| Compliance and approval | What evidence and approvals the project needs before tender | A verified document set per SKU and a named approving authority | A legal opinion on what the regulation requires |
| Operational readiness | Whether the building can commission and maintain the system | Training record, spares list, maintenance plan | Whether the operator's whole organisation is ready |
A pilot that mixes two families in one building usually produces two half-answers. If the client wants both product-class fit and operational readiness, run them as two passes over the same building, or size the pilot so that one pass produces evidence for both without weakening either.
On wording, the pilot brief should say "the pilot exists to confirm that the selected lock class fits door classes A, B and D under the conditions recorded in the environment log". It should not say "the pilot exists to prove the locks work". A brief in the second form cannot be failed, which means it cannot conclude, and a pilot that cannot conclude becomes a permanent fixture nobody ever closes.
Step Two — Build the Door Population and the Survey
Door fit is the one variable in a UAE hospitality building that no amount of catalogue browsing will settle, because the door population is assembled from several trades that rarely share a tolerance standard. Aluminium and uPVC profiles dominate entrance and corridor doors, heavy timber appears on service and back-of-house routes, and mixed-use buildings add glazed shopfronts and partitions that behave like a different product class.
The method that works is to classify the doors first and survey second. A survey that walks the building door by door produces a long list and no decision; a survey that samples each named class produces a fit envelope you can size the whole building against.
| Door class | Typical UAE occurrence | Minimum pilot sample | Fields that must be measured |
|---|---|---|---|
| A — Guest room and serviced residence entry | Timber and composite leaf in the room corridor | Two leaves per handing, two floors apart | Leaf thickness, backset, stile width, spindle position, mortise depth, handing |
| B — Common area and majlis-style reception door | Timber, glazed panel or double leaf | One of each leaf type | Leaf thickness, latch and strike positions, door swing, closer interference |
| C — Service and back-of-house entry | Timber and metal leaf in a steel frame | Two leaves, including the worst-condition route | Leaf thickness, frame profile, gap, threshold detail |
| D — Glazed shopfront and partition | Glass in an aluminium frame | One per glass build-up | Glass thickness, frame section, door thickness, narrow-edge fit |
| E — Main entrance and revolving or sliding line | Aluminium framed | Not required unless the scope includes it | Whole-assembly behaviour, hold-open, supervision point |
Every class uses the same core fields, and the same field set is used whether the door is in the UAE or elsewhere. The smart lock door measurement guide and smart lock door thickness measurement set out the measurement discipline, and the SLK-9936S door thickness compatibility guide shows what a fit envelope looks like when it is published per model rather than per building.
graph LR
R[Guest room leaf] --> R1[Leaf and mortise survey]
R1 --> R2[Credential matrix row]
C[Common area and majlis style door] --> C1[Access policy note]
C1 --> C2[Common area credential rule]
G[Glazed shopfront and partition] --> G1[Glass and narrow edge fit check]
G1 --> G2[Alternative product class]
B[Back of house and service entry] --> B1[Audit and override record]
B1 --> B2[Maintenance credential rule]
Published fit envelopes are worth quoting into the pilot because they let you check the survey against something. Our own hotel-class anchor, the SLK-9936S, publishes a door-thickness range of 36–100 mm with a 5-pin cylinder and a 3-point latch. Treat that as the yardstick for how specific a competent datasheet should be, and confirm every figure against the dated product page for the specific SKU before it enters a tender document — envelopes differ per model and per variant.
| SLK-9936S published field | Published value | What the pilot survey checks |
|---|---|---|
| Door thickness range | 36–100 mm | Leaf thickness of class A, B and C leaves against the envelope |
| Card technology | RFID Mifare 1 at 13.56 MHz | Whether the resident and staff credential matches the reader |
| Read distance and read time | 0–5 cm and under 0.25 s | Whether the card holder must step away from the door to present |
| Power | Four AA batteries | Whether a battery change falls inside the housekeeping round |
| Audit and event records | Up to 1,000 | Whether the buffer survives a peak event week |
| Emergency access and latching | Mechanical key, 3-point latch | The override path the night team actually holds |
| Body and finish | Stainless steel and alloy, multiple finishes | The finish selected for exposed corridors |
| Software modes | Standalone or centralized database, multilingual | Which mode the pilot building will run |
Two survey findings change the scope more often than any other. The first is a door class nobody put on the survey list that turns out to have a different construction. The second is a hardware conflict: a mortise lock, cylinder set, closer or hold-open already specified by the consultant, which makes the smart lock an addition to a prepared door rather than a replacement. Both belong in the scope card's acceptance rule, because they change what "fit" means for that class. The same fields are laid out for a site team to complete on the door itself in the door thickness and backset variance in the United Arab Emirates survey worksheet.
Step Three — Fix the Credential Model Before You Buy Hardware
The credential decision gets made first and changed last, which is why it belongs early in the pilot. A hotel or serviced residence runs on a small number of credential roles, and every one has a person attached who judges the system by how it behaves at the front desk, not by what the reader does.
| Credential role | Held by | Scope of access | Pilot test that proves it |
|---|---|---|---|
| Resident or guest card | One guest or resident, date-bound | Single unit | Issue, use, expire and re-encode without a site visit |
| Floor or section master | Housekeeping supervisor | Defined floor or section | Issue per shift and recover at shift end |
| Engineering card | Installer, maintenance, contractor | Defined door set | Demonstrate bypass range, then withdraw the card |
| Block master | Events and group booking desk | A defined block of units | Issue a block, cancel it, confirm the units are dead |
| Common area credential | Staff, residents, guests as policy decides | Common areas only | Confirm the reader set and the free-entry rule match policy |
| Emergency and override | Security, night audit | As policy defines | Held under control, logged, not casually duplicated |
| Contractor temporary card | Maintenance vendor | Named door set, expiry date | Expiry enforced without a manual purge |
Two operating realities change the design. The first is that common areas in this region are often arranged as majlis-style reception space, where a visitor is received without a fixed desk. That turns the common-area question from "who opens the door" into "how is a guest without a credential admitted", normally answered by a controlled free-entry rule combined with a staff-issued visitor credential. The second is the credential display question: in residential and staff accommodation, operators commonly report a preference for workflows that do not surface a unit identifier on a reader faceplate, and for staff systems that issue a credential without a visible unit number. Write this as a configuration question — which fields the operator's own systems display, and what the lock indicates at the door — and keep it as a stated operating assumption in the pilot record rather than a general statement about who lives or works in the building.
Timing matters as much as type. Housekeeping rounds, front-desk encoding windows and engineer call-outs are commonly scheduled around prayer times and around the shortened working day in Ramadan, which shifts credential volume into different hours and concentrates it into a shorter window. A pilot that exercises only a daytime weekday workflow will not see the peak the property actually generates, so the desk dry run belongs at the property's busiest realistic hour rather than the installer's convenient one.
The deeper credential design points, including revocation and log handling, are covered in smart lock credential security, with the guest-side detail separated out in smart lock guest credential security.
Step Four — Assemble the Evidence Stack: MOIAT, ECAS, G-Mark
This is where the UAE differs from most markets, and it is where a pilot that skipped its homework becomes expensive. Buyers here meet a conformity architecture with several named routes inside it, and the commercial mistake is assuming one route covers the whole shipment, or that a mark printed on a product settles the question.
The routes a UAE importer typically encounters sit alongside the Saudi certificate-of-conformity route and the GCC G-Mark scheme for a defined list of low-voltage electrical equipment. The questions a pilot must ask, and the evidence it must demand in return, are these.
| Question the buyer asks | Evidence to demand before the pilot verdict | Who can answer it |
|---|---|---|
| Does this specific SKU fall inside a listed scope, and which one | The document set that applies to that SKU, with its scope stated | The supplier, against the published scheme scope |
| What does the moiat-ecas document set contain for this model | The certificate or registration documents naming the model, with issue dates and reference numbers | The supplier and the importer of record |
| Is a G-Mark route relevant here | A scope statement for the SKU, not a general assurance | The supplier; treat the scope as per-product |
| Who signs off on the door assembly for life safety | Written confirmation from the named approving authority for the building | The consultant and the authority |
| Which evidence type am I actually holding | The document itself, identified by type | The supplier |
The last row is the one most often skipped. A buyer who hears "the product has certification" may be holding a marketing image, a self-declared declaration of conformity, a test report on a sample, a third-party certificate with a stated scope, or a certificate covering the exact variant being purchased. Only the last settles a procurement question. Ask which one is in the file, and ask for the number, the scope and the date. For uae smart lock pilot scope, the position on this ladder is what the purchase decision turns on.
CONFIRM-WITH-LOCAL-IMPORTER-OF-RECORD — which party in this shipment carries the registration, declaration and marking obligations for the specific SKU, and which document set the destination authority expects before clearance.
CONFIRM-WITH-LOCAL-FIRE-SAFETY-AUTHORITY — confirm which authority signs off on the door assembly, and whether the electronic lock, the closer, the hold-open and the exit device are assessed together as one assembly rather than as separate products.
Never write a scope statement as an assertion that a market bans, mandates or certifies a particular lock. The honest and more useful formulation is the question and the evidence: which scheme covers this SKU, what does the file contain, who confirms the scope. A close reading of that file, document by document, is in reading a Moiat-Ecas document set for smart locks, and the importer's side of the same file is covered in smart lock importer guide.
Step Five — Prove the Environment: Heat, Dust, Power
Two environmental facts about the region change how a pilot should be designed. Ambient temperature runs high for much of the year, and dust is a persistent condition on exterior doors, service corridors and unconditioned approaches. Both are ordinary engineering topics, and both are invisible at sample stage because the sample was tested in a conditioned room.
The honest position is that a lock's behaviour in heat and dust is a property of the specific model and version, verified on the dated product page for the SKU rather than assumed. What the pilot can do is establish the conditions of your building and require the supplier to answer against them in writing.
| Condition to establish for the pilot building | What to ask the supplier | What the pilot records |
|---|---|---|
| Highest ambient temperature the lock will see, and for how long | The published operating envelope for that SKU | Measured site conditions, not regional averages |
| Dust exposure by door class | Sealing and ingress-protection statement for that model | Which classes are sheltered and which are not |
| Whether the lock draws from the door or from a central supply | The power architecture and the battery or supply format for that model | Which doors need a maintenance visit, and how often |
| How a power interruption affects the door state | Behaviour on low battery and on supply loss | The fallback path the operator will rely on |
| Change-out interval against the housekeeping round | Whether the round can absorb the change | Round length and access to the batteries |
The battery question is where environment becomes operational cost rather than a specification detail. A lock on an exterior aluminium entrance in a warm unconditioned vestibule does not consume power at the same rate as one on an interior timber room door, and a pilot that averages the two hands the operator a battery-change plan that fails on the doors that need it most. The published envelope is in smart lock working temperature, and the test sequence for these conditions is set out in high ambient temperature and sand and smart lock reliability in the United Arab Emirates.
Where a supplier claims an operating range, an ingress rating or a cycle figure, ask for the underlying test report rather than the datasheet line. A published figure without a report behind it is a claim; the same figure with a dated report and a stated test condition is evidence. The evidence ladder that separates the two belongs in the pilot file, because it is the same ladder used at factory-acceptance stage in the hotel smart lock sample testing guide.
Step Six — Run the Approval Chain: Submittal, Mock-Up and Sign-Off
Projects in this region are contractor-led, consultant-approved and frequently tender-packaged. A smart lock therefore does not move from sample to building on a purchase order; it moves through a submittal, often a physical mock-up, and a written approval, each with its own owner and format.
The pilot should run inside that chain rather than around it, which means treating the mock-up as the single most valuable hour the pilot spends. A mock-up is the first moment a consultant can see faceplate, credential reader, indicator, door gap and openable hardware together on a real door, and the last moment at which changing the product class is cheap.
| Chain stage | What enters it | What the pilot must contain | Typical owner |
|---|---|---|---|
| Submittal | The proposed model against the door schedule | Datasheet, fit envelope, conformity file, finish sample | Contractor or consultant, depending on contract form |
| Mock-up | One installed unit on a representative door | Installation record, fit measurements, operation check, finish sign-off | Consultant with the approving authority present |
| Approval | Written response to the submittal | A dated response with comments closed or carried | Consultant or authority |
| Installation | Released quantities | Per-door commissioning record and defect log | Contractor and integrator |
Two findings recur. The first is that the approval authority is not always the party that nominated the lock: if the integrator sources and the consultant approves, the evidence file has to be built for the consultant's reading, not the integrator's convenience, and the role split between them is set out in smart lock manufacturer for system integrators. The second is that life-safety doors pull the hardware package into a single assembly assessment, so a lock approved in isolation can still require a re-submittal once it is shown on an exit door with a closer and a hold-open fitted.
CONFIRM-WITH-LOCAL-CIVIL-DEFENCE-AUTHORITY — whether the electronic lock may be used on this door type in this occupancy, and whether the approval attaches to the door assembly or to the product, in the form the authority actually issues.
The approval file is the artefact that most often converts a pilot from a cost into a saving. If the pilot building has already produced a signed mock-up approval, the next building's submittal inherits that work. If the pilot skipped it, every building starts from zero. The submittal and mock-up chain is set out in smart lock OEM sample approval, and the egress and life-safety questions behind it in the United Arab Emirates egress rules and electronic locks.
Step Seven — Set the Documentation, Language and Training
The last scoping step decides whether the building can run what has been installed. Three deliverables belong in the scope card from the start, because each is cheaper to specify during scoping than to retrofit after handover.
Documentation is bilingual. Arabic and English manuals, labelling and software interfaces are commonly required in this market, and the requirement reaches further than the box: the installer needs a commissioning sheet in both languages, the housekeeping team needs a one-page operating card, and the front desk needs the software workflow explained in the language it will be used in. The smart lock OEM installation documentation record shows the document set a manufacturer should be able to produce per model, and that is the reference to demand from any supplier.
Training is a scoped item with a sign-off, not a courtesy. The deliverable should name the audience, duration, language, competence being built and the sign-off. For hospitality that is usually two audiences: the front-desk and night-audit team that operates the credentials, and the engineering or maintenance team that changes batteries and handles overrides. A pilot that trains only the installer has designed an operations problem rather than solved one.
The third deliverable is the maintenance and spares plan, written while the pilot building is still standing: which parts are consumable, how many the property should hold, who replaces them and at what point in the maintenance round, and which failures need a technician rather than a housekeeper. Spare-parts planning here is affected by how the channel is structured, since parts may travel through a free-zone trader or a mainland distributor, and that changes the lead time the operator should design around.
The Pilot Scorecard: Comparing Candidates on Pilot Evidence
At the end of a pilot the decision is rarely about the lock that looked best in the mock-up. It is about which candidate produced the most complete evidence, because that is the candidate that can survive a consultant's submittal review and a tender pack. Score the evidence, not the impression.
| Criterion | Weight | Score 2 — evidenced | Score 1 — asserted | Score 0 — absent |
|---|---|---|---|---|
| Fit envelope against measured door classes | 3 | Published envelope plus pilot measurements covering every in-scope class | Envelope published, not checked against the survey | No envelope given |
| Conformity document set for the SKU | 3 | Named documents with numbers, scope and dates | A general assurance covering the range | Nothing for the SKU |
| Door assembly approval path | 3 | Named authority, written confirmation, mock-up signed | Authority named, no written response | Not addressed |
| Environment and power behaviour | 2 | Stated envelope plus a test report or pilot observation | A claim without a report | Not addressed |
| Credential model fit | 2 | Working matrix with a desk dry run and a lost-card procedure | A described workflow only | Not addressed |
| Documentation and language | 2 | Bilingual document set delivered and indexed | Partial set | Not addressed |
| Training and maintenance readiness | 1 | Training plan with sign-off, spares list, maintenance plan | Verbal commitment | Not addressed |
| Supplier verification and audit trail | 1 | Verification completed, audit or factory record supplied | Claimed | Not addressed |
A zero is not a tie. A zero in the first three rows means the candidate cannot be carried into a tender pack, and performance elsewhere does not compensate. The verification and audit discipline behind that last row is described in smart lock supplier verification China and smart lock factory audit China, and it is worth running before the pilot: a failed audit two weeks before a verdict wastes the whole pilot.
Where UAE Pilots Fail
Most pilot failures are process failures, and they repeat. The list below is written as the version a buyer recognises from the last project.
| Failure mode | What it looks like | Prevention in the scope card |
|---|---|---|
| Scope creep | Door classes added during install until the pilot covers the whole building and proves nothing | Fixed class list with a sampling rule and a written change route |
| Sample-only evidence | Conclusions drawn from units on a workbench, not on building doors | Named mock-up requirement with a dated approval record |
| Unmapped door population | A door class nobody surveyed appears on site | Class list fixed against the door schedule before sampling |
| Conformity file assembled late | Documents requested after the verdict date, blocking approval | Document set listed as an acceptance precondition |
| Pilot treated as a discount order | Volume bought, evidence skipped, no verdict issued | Written acceptance rule naming a signer and a date |
| Battery plan averaged across the fleet | Change-out routine fails on the hottest, dustiest doors | Per-class power plan built from site conditions |
| Training left to the installer | Front desk cannot issue or recover a credential in normal operation | Named audience, named deliverable, sign-off |
| Verdict with no carry-forward | Findings vanish; the next building starts again | Carry-forward clause naming the artefacts and their location |
| Approval assumed, not confirmed | Authority position discovered during tender | Written confirmation obtained during the pilot |
An Illustrative Pilot: 96 Serviced Residences Above a Mixed-Use
The scenario below is illustrative, written to show the scope card working, not to describe a real customer.
Consider a 96-unit serviced residence on the upper floors of a mixed-use tower, with retail at grade and a glazed entrance line at street level. The operator has a card-based front desk, housekeeping on a shift rota, and a contractor who has already specified door hardware for the residential floors. The integrator is asked to pilot before the order for the remaining phases.
| Scope card line | Entry for this building |
|---|---|
| Decision under test | Confirm the lock class and credential model fit the residential entry doors and the shared amenities, and produce the submittal-ready evidence file for the consultant |
| Covered door classes | A residential entry leaves, C service and back-of-house leaves, D glazed entrance and partition doors; class B common areas sampled once |
| Exclusions | Retail shell doors, plant access, car park barriers, and any door with an existing consultant-specified electronic lock |
| Evidence set | Survey sheet, mock-up approval, moiat-ecas file for the shortlisted SKU, environment observation log, credential matrix with desk dry run |
| Acceptance rule | The consultant's hardware reviewer signs the mock-up record with no unmapped class and no open safety comment; the operator's general manager signs the credential dry run |
| Carry-forward | Survey workbook, mock-up record and document file go to the tender pack for the remaining phases |
The survey returns a finding that changes the plan: the service corridor doors are heavy timber with a different mortise than the residential leaves, so class C cannot be covered by the class A hardware, and the scope card is amended through the written change route rather than silently. The mock-up finds the glazed entrance needs a different product class again, and the credential dry run shows front-desk staff had been assuming a different workflow from the residential portal.
Three findings, one building, one month of pilot time. Each would have been a change-order conversation in phase two; each is now an entry in the evidence file with a date and a signature. The hotel smart lock project planning guide is the canvas format to copy, and the hotel smart lock RFQ guide is where the resulting specification gets written up.
The Artefact Pack: What Leaves the Room With You
A pilot is worth what its artefacts are worth, because artefacts survive the people who produced them and travel into the next tender pack. Ten documents should exist at the end of a pilot, each with a named owner and a signature.
| Artefact | What it is | Who signs | What it unlocks |
|---|---|---|---|
| Scope card | The one-page definition of the pilot | Buyer, integrator, operator | The pilot's mandate and its close |
| Door survey workbook | Measurements per door class, with photographs | Site surveyor, integrator | The fit decision and the order quantities |
| Fit assessment note | Survey mapped against each shortlisted model's envelope | Integrator | Model selection |
| Mock-up record | Physical installation, measurements and operation on a real door | Consultant and approving party | The submittal for every later building |
| Credential matrix | Roles, scopes, expiry rules and the desk dry run | Operator's front-desk manager | The credential policy into phase two |
| Conformity evidence file | The document set per SKU, with scope, numbers and dates | Importer of record | Clearance and tender submission |
| Environment and power log | Site conditions, power architecture, change-out plan | Integrator and maintenance lead | The maintenance regime |
| Training and commissioning pack | Bilingual documents, training record, commissioning checklist | Contractor and integrator | Handover without a service tail |
| Spares and service plan | Consumable list, holders, replacement route | Operator's maintenance lead | Stocking and service response |
| Carry-forward register | Every finding, its owner and its destination in phase two | Project manager | The next tender pack |
Keep the pack in one place with a fixed index, and close the carry-forward register last. A pilot that produces nine artefacts and an uncaptured lesson is worth less than a pilot that produces eight artefacts and a written decision.
From Pilot to Rollout: Phase-Two Decision Rules
The point of a pilot is the decision it enables, so the scope card should say what happens next in each outcome. Three outcomes are realistic, and each has a rule that should have been written before the pilot started.
| Outcome | Meaning | Phase-two rule | Trigger |
|---|---|---|---|
| Extend | The model, credential model and evidence file all hold | Carry the same model and file into the next building; re-run only the survey and mock-up | Signed acceptance rule met with no unmapped class |
| Rework | One dimension failed while the rest hold | Re-open that dimension only, with a defined re-test, in the same pilot building | One criterion scored 1 or 0 with a fixable cause |
| Stop | The product class, or the credential model, is wrong for this operator | Change the class or the model, then pilot again from the scope card | Two failed criteria, or a failed approval path |
Two rules travel with any extend outcome. The first is that the pilot's approval carries only as far as the building it was signed for: a mock-up approval is evidence about a door and an assembly, not a blanket approval for every door type in the portfolio, so each new door class still needs a sample and a sign-off. The second is that the survey is a snapshot — a second building, phase or operator can have a different door population, and re-using the first building's measurements as if they described the second is one of the most expensive shortcuts in this market.
What should carry forward is the evidence set, the credential model, the document file and the acceptance rule — the parts that are true of the programme rather than of the building.
Questions Buyers Ask Before Scoping a UAE Pilot
How many doors should a first pilot building have? Enough to cover every door class that behaves differently, and no more. Two leaves per handing in the guest-room class, two in the service class and one of each unusual build-up usually makes the survey decisive. Volume beyond that buys nothing unless pricing is the stated purpose.
Can the pilot run on a building that is already fitted? Yes, and it often should. A retrofit pilot on occupied units is where the crew learns the real constraints — how long a battery change takes, how the installer works around a fitted door, whether the operator's own team can commission the hardware — because those are the constraints a new-build pilot hides.
Should the pilot use the same lock as the proposed rollout? If the purpose is to test a product class, the pilot should use a unit from the intended production batch, not a showroom sample. If the purpose is to test a different door class, the pilot may deliberately run different hardware, provided the scope card says which question each building answers.
Who owns the data in the pilot? Write it down. The event log the pilot produces contains named access events, and the retention period, hosting location and export rights are procurement questions, not software details. Settle them on the pilot rather than discovering them when the log becomes a dispute.
What happens if the pilot reveals the wrong product class? The scope card should already name the re-test and the stop condition. A pilot that discovers this in week eight has still produced something useful, but only if the mechanism for acting on it was agreed in advance.
How do you handle a credential model the operator rejects? Re-scope the credential matrix, not the hardware. Role list, expiry rules and display fields are the variable here, and the credential mechanics underneath them are covered in how to choose hotel smart locks.
What is the commonest reason a UAE pilot does not conclude? An acceptance rule that was never written. Everything else is recoverable; that one turns the pilot into an installation nobody closes.
The next step is a conversation with the supplier about the scope card rather than about quantities. The smart lock RFQ guide for international buyers turns a scope card into an RFQ, the factory side of the pilot is covered in smart lock factory sample testing guide, and commercial options are quoted per project — send the scope card to request a quote once the door classes and the acceptance rule are written, and ask for samples through order samples against the same card.

