Smart Locks for Student Apartments
Student accommodation is dated before it is specified. The lock conversation is the easy half; the hard half is a calendar: 140 contracts starting and ending on the same weekend, credentials that must die on a Tuesday at midday because the fire officer said so, three vacation windows when the building empties and someone must still walk it, and an intake weekend where forty-seven doors have to work before a queue disperses. This article is the instrument for that calendar. It is a fill-in workbook: five worksheets, one decision matrix, one readiness scorecard, and a roll-up that converts completed pages into a sample order and a quote brief.
Direct answer: smart locks for student apartments succeed or fail on credential lifecycle management, not on lock features. Before choosing hardware, an operator needs six completed documents — an academic-year calendar with exact contract and vacation dates, a per-room credential issue/expire calendar, a vacation-period access audit, a damage-and-wear survey grid scored per door, an intake-day drill sheet rehearsed against the busiest arrival day, and a model spec-capture sheet whose blanks are filled from dated product pages. This workbook provides all six as templates with EXAMPLE rows from an illustrative 140-room scheme; you supply your own dates, rooms and measurements.
Who fills this in: the accommodation manager or lettings lead who owns the contract calendar, one technician who walks the doors with a tape and a clipboard, and the reception supervisor who runs intake. Anyone with access-control hands on the building can read a completed page in one pass and tell you which rooms are ready, which need door works first, and which need a different credential lane.
How This Workbook Works: Ownership, Rules, Cell States
Five rules, then the legend.
Rule 1 — dates come from your contract, not from this page. Every EXAMPLE date is drawn from the illustrative 2026–27 academic year in Worksheet 0. Replace all of them from your own tenancy schedule before the sheets mean anything.
Rule 2 — one row per credential batch, never one row per student. Student cohorts move in bands. A batch row covers a room range (e.g. EXAMPLE A101–A116) so a re-issue or a mass expiry is a line you execute, not a list you retype when half the building's cards should be dead.
Rule 3 — the survey describes buildings, not products. Lock-side numbers live only on Worksheet 5, and every Worksheet 5 cell starts blank. Nothing on Worksheets 0–4 may quote a product claim.
Rule 4 — a blank is a finding. An empty required cell means the audit is not done, not that the answer is unimportant. The readiness scorecard treats blanks as failures.
Cell-state legend used throughout:
CALENDAR— you copy this from your tenancy/academic calendar.Example:— filled planning value from the illustrative 140-room scheme; replace it.Leave blank— walk the door or open the dated product page and enter the value.Ask supplier— a question that must be answered in writing against a specific model, resolved on the dated product page or datasheet, never assumed.
Worksheet 0 — The Academic-Year Calendar This Scheme Assumes
Everything downstream keys off these rows. The illustrative scheme: three flats — Flat A (48 rooms, A101–A148), Flat B (47 rooms, B201–B247), Flat C (45 rooms, C301–C345) — 140 rooms total, mixed cohort occupancy, one reception, card-led room credentials with mechanical key override at the desk.
| Period / Event | Start | End | Days | What It Forces on the Lock Side |
|---|---|---|---|---|
| Tenancy year 2026–27 | Sat 1 Aug 2026 | Sat 31 Jul 2027 | 365 | Credential validity windows align to these dates, not term dates |
| Batch issue / encoding day | Fri 21 Aug 2026 | Fri 21 Aug 2026 | 1 | All 140 room credentials (or the intake-weekend subset) encoded, bench-tested, logged |
| Intake weekend | Fri 4 Sep 2026 | Sun 6 Sep 2026 | 3 | EXAMPLE arrivals 45 / 60 / 30 per day; 5 international residents Mon 7 Sep |
| Teaching block 1 | Mon 14 Sep 2026 | Fri 11 Dec 2026 | 90 | Normal audit mode: event checks weekly, low-battery sweep before break |
| Winter vacation | Sat 12 Dec 2026 | Sun 3 Jan 2027 | 23 | Full-access audit window 1 (see Worksheet 2) |
| Teaching block 2 | Mon 4 Jan 2027 | Fri 12 Mar 2027 | 68 | Resume mode: return-wave log check Mon 4–Fri 8 Jan |
| Spring vacation | Sat 13 Mar 2027 | Sun 11 Apr 2027 | 30 | Full-access audit window 2; mid-year wear spot-check |
| Teaching block 3 / exams | Mon 12 Apr 2027 | Fri 4 Jun 2027 | 54 | Extended-stay survey opens; quiet-building discipline on logs |
| Renewal / extension survey | Mon 12 Jul 2027 | Fri 23 Jul 2027 | 10 | Split graduating vs continuing cohorts; write extensions or hold lines |
| Check-out day | Sat 31 Jul 2027 | Sat 31 Jul 2027 | 1 | All 140 room credentials expire 12:00, grace to 14:00; masters recalled and recounted |
| Inter-tenancy works window | Sun 1 Aug 2027 | Thu 2 Sep 2027 | 33 | Wear-grid repairs execute; vacant-room credentials stay dark |
| Next batch issue day | Fri 20 Aug 2027 | Fri 20 Aug 2027 | 1 | 2027–28 cards encoded against the new tenancy year |
| Next intake weekend | Fri 3 Sep 2027 | Sun 5 Sep 2027 | 3 | Drill sheet re-run with the observed numbers from this year |
Copy this table into your own spreadsheet, replace every date, and add your institution's actual exam-week and graduation dates. If your contract year is 44 weeks instead of 12 months, say so here first — the credential expiry arithmetic downstream assumes tenancy-end drives expiry.
Worksheet 1 — Per-Room Credential Issue / Expire Calendar
One row per batch. The discipline this sheet enforces: every credential in the building has an issue date, an activation moment, an expiry timestamp and an execution method, and no row is complete until all four exist.
| Batch ID | Flat / Rooms | Cohort Example: | Issued (encoded + bench-tested) | Activates | Expires (exact time) | Grace / Exception | Execution Method |
|---|---|---|---|---|---|---|---|
| EX-01 | A101–A116 (16 rooms) | Third-year, exam finishers | Example: Fri 21 Aug 2026 | Example: Fri 4 Sep 2026, 09:00 (arrival) | Example: Sat 31 Jul 2027, 12:00 | To 14:00 same day, desk-logged only | Card batch re-encode; card returned at check-out |
| EX-02 | A117–A132 (16 rooms) | Third-year, project deadline 25 Jun 2027 | Example: Fri 21 Aug 2026 | Example: Fri 4 Sep 2026, 09:00 | Example: Sat 31 Jul 2027, 12:00 (tenancy, not deadline) | None | Same as EX-01; deadline ≠ expiry — do not shorten on the calendar |
| EX-03 | A133–A148 (16 rooms) | Second-year continuing | Example: Fri 21 Aug 2026 | Example: Sat 5 Sep 2026 | Example: Sat 31 Jul 2027, 12:00 → renewal line written during survey week if continuing | Renewal executed on new batch, not extension of old row | Renewal = re-issue under 2027–28 batch, never an edit |
| EX-04 | B201–B223 (23 rooms) | Second-year | Example: Fri 21 Aug 2026 | Example: Sat 5 Sep 2026 | Example: Sat 31 Jul 2027, 12:00 | To 14:00 | Card batch |
| EX-05 | B224–B247 (24 rooms) | First-year | Example: Fri 21 Aug 2026 | Example: Sat 5 Sep 2026 | Example: Sat 31 Jul 2027, 12:00 | To 14:00 | Card batch; PIN fallback issued same slip |
| EX-06 | C301–C322 (22 rooms) | First-year | Example: Fri 21 Aug 2026 | Example: Sun 6 Sep 2026 | Example: Sat 31 Jul 2027, 12:00 | To 14:00 | Card batch |
| EX-07 | C323–C345 (23 rooms) | First-year, late arrivals | Example: Fri 21 Aug 2026 | Example: Sun 6 Sep 2026 + Mon 7 Sep (5 rooms) | Example: Sat 31 Jul 2027, 12:00 | Late-arrival rows activate at their own check-in, cards pre-encoded and sealed | Two activation stamps on one batch row — record both |
| ST-01 | Staff masters × 6 | Reception + night | — | Rolling | Per shift roster; recount every check-out day | N/A | Ask supplier how master credentials are disabled for a departed staff member on your shortlisted model |
| CT-01 | Cleaning crew (Mon/Thu) | Contract | — | — | Example: Expires Fri 11 Dec 2026 and Fri 12 Mar 2027 ahead of each vacation; re-issued on return | N/A | Time-bounded contractor cards, not shared codes |
| CT-02 | Maintenance / contractors | Ad hoc | — | Per job | Example: Single-day validity written on the work order | N/A | — |
| — | BLANK — add your bands | — | — | — | — | — | — |
Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.
Three execution notes from fifteen-plus years of watching access projects go sideways in multi-tenant buildings:
Expiry is a timestamp, not a season. "End of term" is not an expiry. Batch EX-02 above shows why: a project deadline in June does not move a July tenancy expiry, and writing the wrong date into the calendar creates either a building full of ghosts (credentials alive after departure) or a lockout incident at the desk (credentials dead while the contract lives).
Renewal is re-issue. A continuing student gets a new row on a new batch keyed to the 2027–28 tenancy year, not an edit to a 2026–27 row. Edits cannot be audited; re-issues can.
The re-encoding path is a Ask supplier item. For any shortlisted model, ask in writing: if a card fails or a batch must be re-cut mid-year, what is the re-encode procedure, what does it need (encoder, spare cards, laptop, admin PIN), and how long does 140 rooms take? Capture the answer on Worksheet 5 before ordering, not on intake weekend.
Worksheet 2 — Vacation-Period Access Audit
Two full audits per year (winter, spring) plus the inter-tenancy window, run against a fixed question set. Enter Result as PASS / GAP / ACTION, with a name and date on every line. A GAP with no named owner is the finding that surfaces during the next incident review.
Direct answer for the audit owner: the vacation audit checks four things in order — that departed-cohort credentials that must be dead are actually dead (staff, contractors, extensions), that resident credentials that must stay alive still work when nobody is in the corridor to notice otherwise, that the building's empty-window monitoring (event records, low batteries, fire-plan access) is set up before the window opens rather than discovered after it closes.
| # | Audit Item | Window | Why It's on This Sheet |
|---|---|---|---|
| 2.1 | Contractor + cleaning credentials expire BEFORE the building empties (EX Example: Fri 11 Dec 2026 for winter; Fri 12 Mar 2027 for spring) and are re-issued on return | Winter, Spring | Third-party staff are the highest-risk live credentials in an empty building |
| 2.2 | Staff master recount: every master card physically collected, counted, serials logged; night-shift masters locked in the safe procedure per your policy | All three windows | Masters multiply silently; an unrecovered master from last year is a key under the mat |
| 2.3 | Sample test: present a departed-cohort credential (returned at a prior check-out, if one is held for testing) at one lock — confirm rejection; log lock ID | Winter, Spring | Proves expiry actually executes on hardware, not only in the batch schedule |
| 2.4 | Low-battery sweep of all 140 rooms before each vacation (EXAMPLE target: complete by Example: Fri 4 Dec 2026) | Winter, Inter-tenancy | A lock that dies mid-winter-vacation is found in January, with the student already locked out of the plan |
| 2.5 | Event-record / usage-log export or review per your policy, covering the vacation window; anomalies assigned | Winter, Spring | An empty building should show near-zero room events; a log that cannot be checked during the window should be checked before and after |
| 2.6 | Fire/emergency access plan reconfirmed: which mechanical keys open which doors, held where, matching which roster | All three windows | Standalone locks keep the mechanical fallback honest — verify it is actually reachable when the building is half-empty |
| 2.7 | Vacant-room state check at audit start: rooms with no credential issued since last check-out must present dead locks (or sealed credential slips) | Inter-tenancy | The 33-day works window is where stale or never-recalled credentials surface |
| 2.8 | Battery-format stock confirmed for the sweep and intake spares per your consumables policy (Ask supplier battery format and low-power behavior of each shortlisted model — Worksheet 5) | All three windows | The sweep fails if the wrong cells were bought; the format is a dated product-page fact, not a memory |
| 2.9 | Desk procedure check: temporary credential for a resident who returns mid-vacation (lost card at the door on Example: Tue 22 Dec 2026) — who authorizes, what is issued, how is it logged and killed | Winter, Spring | Breaks are not empty buildings; they are buildings with fewer people watching |
| 2.10 | Worksheet 1 reconciliation: every batch row's expiry timestamp compared against what the hardware now accepts, sampled per flat | All three windows | The calendar is only real once the locks agree with it |
The inter-tenancy window (Sun 1 Aug – Thu 2 Sep 2027 in the EXAMPLE calendar) is where Worksheet 3 gets walked: no residents present, all doors openable by staff, technicians working flat-out for 33 days.
Worksheet 3 — Damage-and-Wear Survey Grid
Walk a representative room band per flat during the inter-tenancy window — EXAMPLE: 12 rooms from each flat (A101–A112, B201–B212, C301–C312), 36 rooms, ~26% of stock. Score each element 0–4 per the key below. The grid is rows = elements, columns = sampled bands; extend columns to every room if your policy is full-coverage.
Rating key: 0 = as new · 1 = cosmetic, no function loss · 2 = functioning, monitor · 3 = degraded function, schedule works · 4 = failed or unsafe, immediate works.
| Element Inspected | What is documented |
|---|---|
| Exterior handle / grip: play, wobble, grip-to-open looseness | — |
| Reader window / keypad face: scratches, delamination, wear-through of markings | — |
| Thumbturn / interior lever | — |
| Latch + deadbolt throw: smoothness on 10 cycles per door, count of doors failing | — |
| Strike plate + frame recess: screw pull-out, misalignment from door movement | — |
| Door closer tension + hinge sag (prop-open history in student halls) | — |
| Door condition: warping, thickness change, edge compression around the body | — |
| Battery compartment: seal integrity, corrosion, lid fit | — |
| Emergency keyway: turns freely with the desk key, no damaged cylinder | — |
| Credential slip / spare card condition at check-out inventory | — |
Read the grid two ways, and record both:
Per-door severity. Any element scoring 4, or latch/throw failing its 10 cycles, is an immediate-works room; it cannot be counted on for intake weekend in 33 days unless the works are scheduled inside the works window.
Per-element pattern. A row where all three bands score 2–3 is not thirty maintenance tickets — it is a specification error. Scratched reader faces across every band mean the finish or window material is wrong for this traffic; a battery-correlation row means the format or the sweep cadence is wrong. Patterns feed the next procurement round, and the honest place to resolve what a replacement element costs in hardware terms is /request-a-quote, after the pattern tells you what quantity and what class you actually need.
Wear data also carries a hard rule for student stock: the lock is not the door. A band averaging 3+ on door condition needs a joinery conversation before a hardware conversation; no smart lock holds against a warped slab. Record Y in the last column and route those rooms to the door-works list first.
Worksheet 4 — Intake-Day Drill Sheet
Pick the heaviest arrival day from Worksheet 0 — EXAMPLE: Sat 5 Sep 2026, 60 arrivals — and rehearse it as a timeline before the batch is ordered, then run it live and write what actually happened in the Observed column. The drill's value is the delta between columns.
| Time Slot | Planned Action | Who Owns It | Trigger → Response Failure Modes |
|---|---|---|---|
| Example: 08:00 | Credential desk opens: batch slips per room band, pre-encoded cards staged, bench test of 5 random cards from each batch | Reception supervisor | Cards untested → dead-on-arrival at door; missing slips → queue stalls |
| 08:30 | Encoder station ready with re-encode procedure printout and 10 spare cards per flat; admin credentials verified on two test locks | — | Re-encode path untested → 15-minute fixes become hour-long |
| 09:00 | First arrivals: A117–A148 + B201–B247 bands (EXAMPLE 39 rooms) checked in; activation confirmed at the lock on first use, not at the desk | Check-in team | Desk thinks active, lock disagrees → the single most common intake incident |
| 09:00–17:00 rolling | PIN fallback issued on the same slip as the card for every first-year band (EX-05, EX-06, EX-07) | Desk staff | Card lost day one with no fallback = lockout + forced entry conversation |
| 10:00 | Corridor overflow drill: 20 people at one door in Flat C — how does the queue, the lift call, the luggage lane behave | — | Bottleneck causes propped doors; propped doors cause latch wear you'll read in Worksheet 3 next July |
| 12:00 | Mid-day count: cards issued vs slips vs batch roster; any variance chased NOW | Reception supervisor | Unreconciled by 17:00 becomes a security question at 02:00 |
| 15:00 | Failure-spike review: any room band generating 3+ door failures → suspect batch encoding error, not user error; re-encode whole band as a drill decision | Technician | One confused student is noise; three is a batch fault |
| 17:00 | Last appointments: remaining EXAMPLE 21 rooms of the day checked in; late arrivals routed to Mon 7 Sep procedure | — | After-hours arrivals without a defined path → guard calls |
| 18:30 | Close-out: masters recounted, encoder secured, unreconciled cards quarantined with a written note, day log countersigned | Reception supervisor | The reconciliation you skip is the credential you can't find at next audit |
| Next morning | 24-hour callback check: did every checked-in room's credential still work overnight (temperature, battery handshake, latch settle) | — | Day-one-working / day-two-dead units surface here or at a parent's complaint |
Two structural observations from the factory side of the counter. First, the drill assumes each lock is operated locally at the door — which is how standalone smart locks work; whether any candidate model offers centralized encoding software or remote validity changes is a per-model question to read off its dated product page (some models in the catalog carry PC-side card management at hotel category level; the 24 hotel models are where that method is concentrated — confirm per model, never by category assumption). Second, everything in the failure column is cheap to rehearse in August and ruinously expensive to discover in September with 140 parents present.
Worksheet 5 — Model Spec-Capture Sheet
The only sheet with product numbers on it — and it starts as blanks. Fill one column per shortlisted model from the dated product page or a written datasheet. Any cell you cannot fill from a dated source stays a GAP, and a GAP on a marked line stops that model for that door family.
| Capture Line (what it decides downstream) | What is documented |
|---|---|
| Credential types committed by the model page (card / PIN / fingerprint / key / app) | Notes: Drives the Worksheet 1 lane per door family; app lanes in the catalog include TTLock / Tuya / Doodle on supported models |
| Card / PIN / fingerprint enrollment ceilings (counts) | Notes: 140 residents + staff masters + contractors must fit under the ceiling with headroom for re-issues |
| Admin role structure (how many admins, who holds the erase/encode right) | Notes: Desk vs technician vs manager: this is your intake staffing question |
| Event/audit record capacity and how it is read out | Notes: Worksheet 2 item 2.5 is impossible beyond this depth |
| Door thickness fit band, backset/bore compatibility | Notes: Fill from Worksheet 3 door-condition data, not from the brochure |
| Battery format, low-power warning behavior, failed-battery access path | Notes: Sweep cadence (2.4) and intake risk hinge on this |
| Re-encode procedure, equipment needed, time per 20 cards | Notes: The Worksheet 1 EXECUTION column |
| Mechanical key override: keyway ownership (house keying possible?) | Notes: Fire-plan item 2.6 |
| Centralized software / remote validity: does this model offer it, per its page — yes/no/how | Notes: Do NOT assume; many catalog models are standalone by design. Frame as per-model question only |
| Vacation-time behavior: does expiry execute at the timestamp without anyone touching the lock | Notes: Worksheet 1's expiry column is theater until this line is answered |
| Outdoor/corridor exposure rating claim as published | Notes: Quote the page's own wording; don't upgrade it |
What a well-filled datasheet row looks like. Here is a real published block for the SLK-9936S — a hotel-category RFID model, quoted product-page-documented once, purely as a granularity ruler. Note what it commits and what it does not:
| Field | As Published (SLK-9936S) |
|---|---|
| Door thickness | 36–100 mm |
| RFID | Mifare 1 @ 13.56 MHz |
| Read distance | 0–5 cm |
| Read time | <0.25 s |
| Power | 4 × AA |
| Battery operating cycles | >15,000 |
| Audit/event records | up to 1,000 |
| Cylinder | 5-pin |
| Latch | 3-point |
| Body | stainless steel + alloy, multiple finishes |
| Emergency access | mechanical |
| Management software | multilingual; standalone or centralized database modes |
| Positioning | 1–5 star hotels |
Nothing ports from that block to your student locks — it is a hotel model, and its numbers answer its questions, not yours. The transferable lesson is format: a completed line commits a value, a unit and a scope (door-thickness band, record ceiling, read time, power format). If a candidate product page cannot give you Worksheet 5 lines at that granularity for your doors, you don't have a spec, you have a hope. And note the software line: this hotel model is published with standalone-or-centralized modes — which is exactly the kind of question Worksheet 5 line 9 asks per model, and exactly why you read it off the page instead of assuming it for every lock on a corridor.
Credential-Lane Decision Matrix
Lanes, not models. The catalog spans card, keypad, fingerprint and app/Bluetooth families (79 models: 9 RFID-category, 18 keypad, 37 fingerprint, and app lanes on supported models) — the matrix assigns each door family and population a lane by condition, before any model is discussed.
| Door Family / Population | Default Lane EXAMPLE for this scheme | Acceptable Alternative | Wrong Fit — and Why | Open Question to Resolve on Product Pages |
|---|---|---|---|---|
| Student rooms (140) | RFID card + PIN fallback on same slip | App/Bluetooth for the subset whose model page commits it, as convenience not credential-of-record | Fingerprint as room-credential-of-record in 365-day churn: enrollment/erasure labor per turnover band grows with the roster | Card capacity vs residents + re-issues; expiry-at-timestamp behavior |
| Room doors — accessibility-flagged residents | Model-specific: consider keypad with large tactile buttons or lever-operated class | Lane pairing per resident's documented need | Any lane requiring grip force, small-motor precision or phone ownership the resident doesn't have | Door-fit band on their actual door (Worksheet 3 column) |
| Flat entrance (3 doors) | Keypad or app lane, per your roster model | Card with repeater policy | Card-only if intake shows flat-door fobs migrating off-site | Shared-code rotation: does the model support timed/temporary codes per its page |
| Reception / office strong-room | Staff lane: card or fingerprint (small stable roster = enrollment math works) | Dual-credential policy for high-value doors | Shared PINs of the whole desk — no attribution | Admin-role structure; event records depth |
| Maintenance, contractors | Time-bounded card per job (CT-01/CT-02 rows) | Single-day PIN issued against a work order | Permanent contractor credential — the vacation-audit killer | How a temporary credential is killed without the resident's lock offline |
| Common corridors, bins, plant | Mechanical or simple keying unless a model page commits a credential class for it | — | Don't force a smart credential onto a door the calendar can't maintain | — |
| Post-1000-hrs community-facing doors (if the flat opens doors to residents' guests) | Treat as a different building: see Smart Locks for Residential Communities | — | Room-lane assumptions don't survive a public lobby | — |
The matrix's real job is stopping the one-model-for-140-doors reflex. A scheme this size usually lands on two or three credential families and one or two lock classes, decided by door family — and every "wrong fit" cell is a cost-and-rework conversation avoided before the order, not after installation.
Readiness Scorecard: Does This Building Get to Order?
Tick honestly. Blanks count as failures (Rule 4).
| # | Readiness Gate | Evidence Location |
|---|---|---|
| G1 | Worksheet 0 dates match the actual tenancy schedule (contract start/end, check-out time, vacation windows verified with lettings) | W0, all rows |
| G2 | Every room is inside exactly one credential batch row; no orphans; staff/contractor rows exist | W1 |
| G3 | Each batch row carries issue, activation, expiry-to-the-hour and execution method | W1 |
| G4 | Vacation audit run at least once for the prior period with PASS/GAP/ACTION + owner + date on every item | W2 |
| G5 | Wear grid walked on ≥25% sample per flat; door-works list separated from lock-works list | W3 |
| G6 | Intake drill rehearsed with named owners per time slot; re-encode path demonstrated end-to-end on a test lock | W4 |
| G7 | Worksheet 5 filled from dated product pages for every shortlisted model × door family; no GAP on capacity, fit band or expiry-execution lines | W5 |
| G8 | Mechanical fallback inventory (keys, keyway ownership) confirmed for the building as it exists today | W3 + W5 |
| G9 | Credential-lane matrix reviewed against actual resident-population notes (accessibility, international arrivals, sub-lets policy) | Matrix |
| G10 | Quote brief drafted from roll-up below, quantities by door family, transaction terms left to the quote | Roll-up |
Verdict bands: 10/10 — proceed to samples and quote. 8–9 — fix the named gaps; the order will wait a week, the incident won't. ≤7 — you are not buying locks yet, you are still discovering the building; re-run W2 and W3 before hardware conversation.
Roll-Up: From Completed Sheets to Sample Order and Quote Brief
flowchart TD
W0["Worksheet 0 · academic-year calendar\ncontract dates · vacation windows · intake weekend"] --> W1["Worksheet 1 · per-room credential rows\nissue · activate · expire · execute"]
W1 --> W2["Worksheet 2 · vacation-period\naccess audit"]
W1 --> W3["Worksheet 3 · damage-and-wear grid\nscored per door"]
W2 --> W4["Worksheet 4 · intake-day drill\nrehearsed against the busiest arrival day"]
W3 --> W4
PP["Dated product pages\nmodel spec · see model spec"] --> W5["Worksheet 5 · model spec-capture sheet\nblanks become GAPs"]
W4 --> SC["Readiness scorecard\na blank counts as a failure"]
W5 --> SC
SC --> RU["Roll-up brief\nquantities by door family\nfrom your own completed sheets"]
RU --> SMP["Sample order\nbench-test activation, expiry\nand the failed-battery path"]
RU --> QTE["Quote conversation\ntransaction terms live here"]
The finished pages compress into a short, dated brief. Draft it as follows, with quantities sourced only from your own completed sheets:
Illustrative brief structure (140-room scheme, EXAMPLE values): "Three flats, 48/47/45 rooms. Room-door credential batch: 140 cards + PIN fallback, expiry to your timestamp, re-encode path required per W5 line 7. Three flat-entrance doors on the keypad/app lane. Staff masters × 6, contractor time-bounded × ~10/yr. Door-thickness band measured per flat: your W3/W5 numbers — door fit is the first factory question. Samples requested: quantity by door class, per /order-samples to bench-test activation, expiry execution and the failed-battery path before batch commitment. Transaction terms — pricing, quantities, delivery — verified in writing in the quote against this door-family breakdown."
Notice what the brief does NOT contain: assumed remote-management capability (it's a W5 line per model), a one-lock-for-all-doors premise (it's per door family), or numbers that came from anywhere except your survey. This is also where sibling work converges: the general apartment-buying framing sits in the apartment buildings buyer guide, the day-two operating discipline lives in smart locks for apartment operators, and when the flat's doors start meeting the neighbourhood, smart locks for residential communities picks up that thread.
Order samples against Worksheet 5, not against a spec sheet you liked: the intake drill (W4, 08:30) assumed you had already demonstrated the re-encode path on a real lock on a real jamb. That demonstration needs physical units in hand — /order-samples is the page for that; the committed quantities and terms come out of /request-a-quote once the completed sheets define the door families.
What This Workbook Deliberately Does Not Say
Accountability requires the boundary, and a workbook is where boundaries are cheapest to state.
No prices, minimums, delivery dates or coverage years. Those are transaction documents produced against your completed brief — the quote is the only correct place for them, which is why every quantity in these sheets came from your rooms and none from a supplier promise.
No certification claims and no capability claims on your shortlist's behalf. Model-level specifications — capacities, fit bands, battery behavior, software modes — are only ever "check the model’s published specification." A number that can't be sourced is a GAP, and a GAP blocks the door family.
No remote-locking premise. Most of what works in student corridors is standalone by design: the credential lives on the card and the lock, and the calendar in Worksheet 1 is enforced at encoding time and at expiry behavior you verified in W5. Where centralized software exists (the spec-ruler model above is published with a centralized-database option), it is read per model, per page — the exception being taught, never the rule smuggled.
No substitution for your fire officer or your local rules. Worksheet 2 item 2.6 exists because the mechanical path and the muster plan are not the lock vendor's paperwork — they're yours, and they outrank every convenience feature in this file.
The calendar is the product. Fill Worksheet 0 this week; the hardware conversation gets easier and shorter, and the intake weekend gets quiet. That is the whole thesis — run it through /request-a-quote with your completed roll-up when the scorecard reads 10.

