VidIn CheckList

TEMPLATE-VidIn-Service-Guide

3 min read

<%* // ───────────────────────────────────────────────────────────────────────────── // VidIn Expertise — Field Service Guide Template // Templater tR += pattern (avoids async race conditions) // See _Claude/Obsidian-checklist-CLAUDE.md for pattern notes // // Usage: Run this template via Templater in any VidIn-Expertise folder. // It prompts you for key values and builds the frontmatter + skeleton. // Fill in the [bracketed] placeholders with real content after creation. // ─────────────────────────────────────────────────────────────────────────────

const title = await tp.system.prompt(“Document title”, “dormakaba [Model] — [Procedure Name]”); const vendor = await tp.system.prompt(“Vendor name”, “dormakaba”); const model = await tp.system.prompt(“Model number (or leave blank)”, ""); const appliesTo = await tp.system.prompt(“Applies to (site, equipment, or scope)”, “All VidIn technicians and subcontractors”); const purpose = await tp.system.prompt(“One-sentence purpose”, “Guide field technicians through [procedure] for [equipment]”); const today = tp.date.now(“YYYY-MM-DD”); const todayLong = tp.date.now(“MMMM D, YYYY”);

tR += `--- fileClass: turnstile-doc title: ${title} doc_type: guide status: draft owner: John Lang audience:

  • field-tech
  • pm equipment:
  • turnstile vendor: {model} mounting_type: barrier_type: lane_config: section: 01-Field-Operations last_updated: ${today} review_cycle: quarterly tags:
  • ${vendor.toLowerCase().replace(/\s+/g, ’-’)}
  • service applies_to: {purpose} version: 1

${title}

Applies to: {purpose} Version: 1.0 | Last Updated: ${todayLong} Owner: John Lang

Overview / Purpose

About This Document

[Brief description of the problem this guide addresses and when to use it. Include any critical context a technician needs before scheduling or preparing for this job.]

⚠️ Before You Begin

Pre-Service Requirements

Read this section completely before scheduling service or preparing for this job.

  • [Requirement 1 — e.g. access credentials, permits, escort arrangements]
  • [Requirement 2 — e.g. confirm parts on hand before scheduling]
  • [Requirement 3 — e.g. notify site contact of alarm triggers]

Scope of Work

  1. [High-level step 1]
  2. [High-level step 2]
  3. [High-level step 3]
  4. [Add or remove steps to match the job]

Required Tools & Materials

ItemQtyNotes
[Part or tool name]1[Any notes — part numbers, specs, etc.]
[Part or tool name]1
[Part or tool name]1

Confirm Parts

Verify part numbers and any special tooling requirements with the manufacturer service manual before the service date.

Procedure

1 — [Stage Name, e.g. Site Access & Coordination]

  • [Step]
  • [Step]
    • [Sub-step or note]

2 — [Stage Name]

Warning

[Warning text]

  • [Step]
  • [Step]

3 — [Stage Name]

  • [Step]
  • [Step]

4 — [Stage Name]

  • [Step]
  • [Step]

5 — Testing

  • Restore power / re-enable the system
  • Test through a full operational cycle
    • [Describe what a passing result looks like]
  • Verify all measurements/settings match pre-service state
  • [Sign-off steps — keys returned, paperwork, etc.]
  • Document the completed repair — record part numbers (old and new), technician name, and date

Notes / Gotchas

Lessons Learned

Exceptions, common mistakes, and things learned the hard way.

  • [Note 1]
  • [Note 2]

Last updated: ${todayLong} Owner: John Lang | jlang@vid-in.com`; %>

Graph View