Creating Log Templates
This guide will help you to create a log type template
Creating Log Templates in Storecall
Log templates in Storecall are used to build workflow-driven forms that follow a clear path of statuses across teams or user groups. This is ideal for workflows such as incident reporting, procurement requests, equipment service logs, or customer queries - essentially, any process that needs tracking, handovers, and action by different users.
✨ Getting Started
To create a new log type template:
Navigate to the sidebar and click Templates ▼ > Create Template
You will be prompted with a popup to choose the type of template you'd like to create. Storecall supports 3 template types:
Audit — For checklists and evaluations (e.g., store manager daily checks, regional visit forms)
Log — For process-based workflows that may involve multiple users over time
Approval — For submitting and tracking requests (e.g., leave, item returns, or discounts)
⚠️ For this walkthrough, we'll focus on creating a Log Template.
Template Basics
Template Name: Give your template a descriptive name.
Template Description: Briefly explain what the template is used for.
Template Category: Use categories to organize your templates (e.g., Maintenance, Customer Service, Operations).
Template Access
Assign which user groups are allowed to use this template. Storecall works on a role-based system where users are assigned to groups. By limiting access to templates per group, you ensure that only the right teams see the templates relevant to them.
✉️ Submissions Settings
Configure what happens when someone submits a form:
Users to Email on Submission: Select users to instantly notify via email (includes PDF + any uploaded files/images).
Email Report to Location Email: Automatically email the submission to the location's linked email address.
Require Signature: Enforce a digital signature before submission is allowed.
Select Submission Identifier: Choose a question (e.g., "Client Name" or "Reference No.") to act as the submission identifier for easier tracking.
🗓️ Status Flow: Build Your Workflow Logic
The Status Flow section is where the magic happens:
You can define multiple statuses for your log workflow, such as:
Requested
In Progress
Awaiting Manager Input
Completed
Closed
Each status has the following attributes:
Status Label: What users will see.
State Type: Open (editable) or Closed (read-only).
Allowed From Statuses: Define which statuses can transition to this one.
Allowed Groups: Choose user groups who can change to this status.
Notification Recipients: Select users who should be notified when the status is set.
You can:
Reorder statuses.
Click on any cell to edit a status.
Add new statuses via the Add Status button.
📃 Designing the Template Structure
Use Sections to group related fields. You can:
Click New Section to add a new section.
Within each section, click New Field to add questions.
Field Types
Each field (question) has a type (text, dropdown, file upload, etc.). For each field, you can:
Basic Field Settings
Mark as Mandatory: Force completion.
Allow Files: Enable file uploads on the question.
Allow Actions: Let users log follow-up actions.
Allow Comments: Let users leave comments on the field.
Advanced Field Settings
Show Field on Selected Status: Show the field only when submission is at a specific status.
Auto-update Log Status When Filled: Automatically change the submission to a defined next status when this field is completed.
Mark Field Read-Only After First Fill: Once filled, this field becomes locked (even if the submission remains open).
User Groups Who Can Edit After Submission: Specify which groups can edit the field if it’s not locked.
✅ Final Step: Save Your Template
Once you’ve:
Configured your workflow statuses
Designed sections and fields
Assigned user access
Defined submission rules
...you can click Create Template to save it.
The template is now ready to be used by your organization and follows the status-driven workflow you've designed.
💡 Tip: Real-World Use Cases
Procurement Request Workflow: Requested > Reviewed > Approved > Ordered > Closed
Service Request Log: Logged > Assigned > Technician Visited > Closed
Incident Reporting: Open > Under Investigation > Resolved > Closed
These workflows previously required emails, WhatsApp messages, and spreadsheets to coordinate. Storecall brings them into a single digital workflow with visibility, accountability, and action tracking built-in.
By using log templates, teams can move from chaotic multi-channel workflows to structured, visible, and efficient digital processes — all within Storecall.
Last updated