Lesson 1 of 7 · 3 min
What Are Resources and Why They Matter
Understand what SOPs and checklists are in Vremly, how they differ, and where they live in the platform.
What Are Resources and Why They Matter
Video coming soon
Lesson Notes
Vremly's Resources library is a shared, org-scoped collection of two distinct document types: Standard Operating Procedures (SOPs) and Checklist templates. SOPs are rich reference documents — prose instructions your team reads before or during a shoot. Checklists are interactive task lists your field technicians tick off item by item on a live job. Both live under the Resources section and are accessible to every member of your organization.
SOPs are authored in Markdown, which means admins can use headings, numbered steps, bullet points, and bold text to structure content clearly. When a team member opens an SOP on the web portal or iOS app, the Markdown renders into formatted, readable prose — not raw code. This makes SOPs suitable for multi-step procedures like twilight-shoot setup, drone pre-flight, or gear-pack checklists that don't need per-item tracking.
Checklists are fundamentally different: every item in a checklist can be ticked individually, and that tick state is persisted per-user per-project on the server. This means if a technician starts ticking items on their iPhone at a property, their progress is immediately reflected on the web portal for their project manager to see — and vice versa. A checklist is a living document tied to a specific job, not just a reference read.
The Resources area has two distinct surfaces in Vremly. The admin builder at /resources (visible only to Owners, Admins, and Project Managers) is where SOPs and checklists are created, edited, toggled active/inactive, and deleted. The team-facing portal at /portal/resources is where every org member browses and uses those resources in the field. On iOS, the Resources section is accessed from the More drawer and provides the same library browse experience. These two surfaces — authoring vs. consumption — are intentionally separate so field staff see a clean, distraction-free interface.
Every resource is tagged with one or more topics: Pre-shoot, On site, Gear, Safety, Post-shoot, or Handoff. Topics drive the filter pills on the browse page, letting a technician on-site tap 'On site' and immediately see only the resources relevant to where they are in the workflow. Admins can also tag resources with one or more service types (Photo, Video, Floorplan, Virtual Tour, etc.), and the platform uses those tags to auto-surface the right resources on a matching job — so a video-only job will surface video-specific SOPs without the technician having to search.
Key Takeaways
- SOPs are Markdown reference docs; checklists are interactive tick-lists with per-user per-job state synced across web and iOS.
- Every resource is tagged by topic (Pre-shoot, On site, Gear, Safety, Post-shoot, Handoff) and optionally by service type to auto-surface on matching jobs.
- The admin builder (/resources) and the team portal (/portal/resources) are separate surfaces with separate access controls.
- Resource state — which checklist items have been ticked — is saved server-side and syncs in real time between web and iOS.