Yes — below is a Claude-ready PRD. I designed it for your exact use case: new factory supervisor joins Monday, Docmost will become the SOP hub, and the system should have a one-stop dashboard where he can access production, quality, raw material, stacking, curing, dispatch, reports and improvement suggestions.
Docmost is a good fit because it supports spaces, permissions, groups, nested pages, real-time collaboration, comments, page history, search, attachments, and diagrams like Draw.io, Excalidraw and Mermaid. n8n can later connect Telegram, webhooks and Odoo workflows for process control. ([docmost.com][1])
Maiyuri Bricks Factory SOP Command Center
Create a complete, visual, easy-to-use SOP knowledge hub in Docmost for Maiyuri Interlock Bricks. The system should help the new factory supervisor understand, follow, improve and control daily factory operations from day one.
The output should be a neatly structured Docmost workspace with:
This is not a text-heavy manual. It should feel like a practical factory operating system.
Factory Supervisor
Responsibilities:
Production Labour
Sales/Admin Staff
Management
Create the following spaces in Docmost:
00 Supervisor Command Center
01 Daily Factory Control
02 Raw Material Control
03 Production Process
04 Quality Control
05 Stacking, Curing & Stock
06 Dispatch & Vehicle Planning
07 Sales, Customer Visit & Admin Support
08 Safety & Housekeeping
09 SOP Improvement Register
10 Management ReviewCreate a landing page called:
This dashboard is the single starting point for the factory supervisor every day.
Use cards/sections in this order:
Create quick-access cards:
Each card should contain:
Example:
🏭 Daily Factory Opening
Check machine, labour, material, power, water and production plan before starting work.
[Open SOP]Cards:
Cards:
Cards:
Cards:
Cards:
Display a red alert box:
Call/Inform Ram or Srinivasan immediately if:
- Machine breakdown
- Major quality issue
- Raw material shortage
- Wet/contaminated red soil
- Labour shortage
- Customer complaint
- Dispatch error
- Safety incidentCreate a simple weekly plan:
Monday: Follow opening, planning and raw material SOPs.
Tuesday: Improve raw material separation and moisture control.
Wednesday: Focus on mixing and first 20 bricks approval.
Thursday: Focus on stacking, curing and hold/reject system.
Friday: Focus on dispatch, loading and customer visit handling.
Saturday: Submit SOP improvement suggestions.Every SOP page must follow this exact structure.
SOP Name:
Process Code:
Version:
Owner:
Applies To:
Frequency:
Last Updated:
Review Frequency:One sentence only.
List responsible roles.
Clear trigger condition.
Use Mermaid or Draw.io style flowchart.
Use 5–8 steps only.
Each step should have:
Two-column table.
Short tick-box checklist.
Mention whether to update:
When to inform Ram/Srinivasan.
List common mistakes.
Add:
If you find a better way to do this process, add a comment below or submit an improvement request in the SOP Improvement Register.Create the following SOP pages with the content below.
Process Code: DAILY_OPENING_V1
Owner: Factory Supervisor
Applies To: Factory Supervisor
Frequency: Daily before production starts
Review Frequency: MonthlyEnsure the factory is ready for safe, smooth and planned production before work starts.
flowchart TD
A[Supervisor arrives] --> B[Check labour availability]
B --> C[Check machine and power]
C --> D[Check raw material availability]
D --> E[Check water and tools]
E --> F[Confirm today's production plan]
F --> G{Any issue?}
G -- Yes --> H[Inform Ram/Srinivasan]
G -- No --> I[Start production]
[ ] Labour available
[ ] Machine ready
[ ] Power available
[ ] Water available
[ ] Red soil available
[ ] M-sand dust available
[ ] Cement available
[ ] Work area clean
[ ] Production target confirmed
[ ] Issues reported if anyInform Ram/Srinivasan if:
Process Code: PROD_PLAN_V1
Owner: Factory Supervisor
Frequency: Daily morningPlan what product to produce, how much to produce, and what material/labour is needed.
flowchart TD A[Check stock and orders] --> B[Choose product] B --> C[Set target quantity] C --> D[Check material requirement] D --> E[Assign labour] E --> F[Start production batch]
[ ] Product selected
[ ] Target quantity fixed
[ ] Batch ID created
[ ] Material availability checked
[ ] Labour assigned
[ ] First 20 bricks approval plannedProcess Code: REDSOIL_RECEIPT_V1
Owner: Factory Supervisor
Frequency: Whenever red soil is receivedEnsure only suitable red soil is accepted and stored correctly.
flowchart TD
A[Red soil vehicle arrives] --> B[Take vehicle/material photo]
B --> C[Check visible contamination]
C --> D[Check moisture]
D --> E{Acceptable?}
E -- Yes --> F[Unload in red soil zone]
E -- No --> G[Move to hold/reject decision]
F --> H[Update material receipt record]
G --> I[Inform Ram/Srinivasan]
✔ Take photo before unloading
✔ Keep wet and dry soil separate
✔ Use marked red soil zone
✔ Inform if quality is doubtful✘ Do not unload in m-sand area
✘ Do not mix old and new material without approval
✘ Do not use wet soil without approval
✘ Do not accept contaminated material silently[ ] Supplier identified
[ ] Quantity noted
[ ] Photo taken
[ ] Moisture checked
[ ] Contamination checked
[ ] Correct zone used
[ ] Receipt updatedInform Ram/Srinivasan if:
Process Code: MATERIAL_ZONE_V1
Owner: Factory Supervisor
Frequency: DailyPrevent material mixing, spillover and moisture damage.
flowchart TD A[Material arrives] --> B[Identify material type] B --> C[Unload in marked zone] C --> D[Maintain separation gap] D --> E[Cover/protect if needed] E --> F[Use material batch-wise]
[ ] Red soil zone clear
[ ] M-sand dust zone clear
[ ] Waste zone clear
[ ] Cement storage dry
[ ] No spillover between materials
[ ] Wet material separatedInform management if material is spreading, mixing or absorbing moisture.
Process Code: MIB8_MIXING_V1
Owner: Factory Supervisor
Frequency: Every MIB 8-inch batchEnsure consistent strength, finish and quality of MIB 8-inch bricks.
flowchart TD A[Confirm product: MIB 8-inch] --> B[Check materials] B --> C[Measure recipe] C --> D[Dry mix] D --> E[Add water gradually] E --> F[Check mix consistency] F --> G[Start first 20 bricks]
Add exact approved recipe here:
Red soil: ___
M-sand dust: ___
Cement: ___
Admixture: ___
Water: controlled by moisture condition✔ Mix holds shape
✔ Not too dry
✔ Not sticky/watery
✔ Uniform colour
✔ No lumps✘ Too wet
✘ Too dry
✘ Cement lumps
✘ Uneven colour
✘ Soil stones/waste visibleProcess Code: FIRST20_QC_V1
Owner: Factory Supervisor
Frequency: Every batch/product changeoverStop bad production before large quantity is produced.
flowchart TD
A[Produce first 20 bricks] --> B[Check shape and edges]
B --> C[Check interlock fit]
C --> D[Check surface and cracks]
D --> E{Approved?}
E -- Yes --> F[Continue production]
E -- No --> G[Adjust mix/machine]
G --> H[Produce another sample]
[ ] Edges are sharp
[ ] No visible cracks
[ ] Surface finish acceptable
[ ] Shape is correct
[ ] Interlock fit is correct
[ ] Mix is not too wet/dry
[ ] Supervisor approved continuationPASS = Continue production
HOLD = Adjust and produce new sample
FAIL = Stop and inform managementInform management if two sample attempts fail.
Process Code: HOURLY_PROD_CHECK_V1
Owner: Factory Supervisor
Frequency: Every production hourCatch quality issues early during production.
flowchart TD
A[Every hour] --> B[Select sample bricks]
B --> C[Check visual quality]
C --> D[Check stack count]
D --> E{Issue found?}
E -- Yes --> F[Hold batch / correct process]
E -- No --> G[Continue production]
[ ] Hourly sample checked
[ ] No major cracks
[ ] Edge quality acceptable
[ ] Stack count correct
[ ] Mix consistency acceptable
[ ] Rejection count notedProcess Code: STACK20_SLEEPER_V1
Owner: Factory Supervisor
Frequency: Every production batchStandardize stacking, protect bricks from ground moisture and make counting easy.
flowchart TD A[Prepare stack area] --> B[Place sleepers/base support] B --> C[Stack 20 bricks] C --> D[Keep batch card visible] D --> E[Maintain gap between batches] E --> F[Move to curing/stock stage]
✔ 20 bricks per mini-stack
✔ Sleepers used below
✔ Batch card visible
✔ Gaps between batches
✔ Hold/reject separated✘ Good bricks touching ground
✘ Mixed batches
✘ No batch card
✘ Irregular count
✘ Broken bricks mixed with approved bricks[ ] Sleeper used
[ ] 20 bricks per mini-stack
[ ] Batch card placed
[ ] Batch separated
[ ] Hold/reject not mixed
[ ] Photo taken if requiredProcess Code: VISUAL_QC_REJECT_V1
Owner: Factory Supervisor
Frequency: Every batch and before dispatchSeparate approved, hold and rejected bricks clearly.
flowchart TD
A[Inspect bricks] --> B{Quality status?}
B -- Good --> C[Approved stock]
B -- Doubtful --> D[Hold area]
B -- Bad --> E[Reject area]
D --> F[Management/QC decision]
E --> G[Record rejection reason]
Good shape, no cracks, acceptable finish, correct size, ready for curing/dispatch.Doubtful quality, under-cured, moisture issue, needs management/QC decision.Broken, cracked, poor shape, wrong mix, poor compaction or not saleable.Corner break
Crack
Poor compaction
Wrong size
Interlock mismatch
Too wet mix
Too dry mix
Surface powdering
Colour inconsistency
Handling damage[ ] Batch inspected
[ ] Approved stock separated
[ ] Hold stock marked
[ ] Reject stock moved to reject area
[ ] Reason recorded
[ ] Photo taken for major defectsInform Ram/Srinivasan if rejection is unusually high or if a full batch is doubtful.
Process Code: DAILY_PROD_REPORT_V1
Owner: Factory Supervisor
Frequency: End of each production dayCapture actual production, rejection, stock and issues for management review.
flowchart TD A[Production ends] --> B[Count produced quantity] B --> C[Count rejected quantity] C --> D[Update batch status] D --> E[Record issues] E --> F[Send daily report]
Date:
Product produced:
Target quantity:
Actual quantity:
Rejected quantity:
Hold quantity:
Approved quantity:
Main issue:
Material shortage:
Machine downtime:
Labour issue:
Supervisor remarks:
Photos attached:[ ] Production quantity counted
[ ] Rejection counted
[ ] Hold stock counted
[ ] Batch cards verified
[ ] Issues recorded
[ ] Report sentProcess Code: CURING_MOVE_V1
Owner: Factory Supervisor
Frequency: Per batchEnsure bricks move through curing without mixing, damage or under-curing.
[ ] Batch moved correctly
[ ] Batch card retained
[ ] Curing date recorded
[ ] Hold/reject separated
[ ] Ready date notedProcess Code: READY_DISPATCH_QC_V1
Owner: Factory Supervisor
Frequency: Before dispatchEnsure only approved and ready bricks are dispatched to customers.
[ ] Correct product
[ ] Correct quantity
[ ] Curing complete
[ ] Visual QC passed
[ ] Batch card verified
[ ] Approved for loadingProcess Code: DISPATCH_PLAN_V1
Owner: Factory Supervisor
Frequency: Every dispatchPlan delivery correctly and avoid wrong product, quantity or site delivery.
[ ] Customer confirmed
[ ] Site confirmed
[ ] Product confirmed
[ ] Quantity confirmed
[ ] Vehicle confirmed
[ ] Driver confirmed
[ ] Loading time fixed
[ ] Sales/admin informedProcess Code: LOADING_VERIFY_V1
Owner: Factory Supervisor
Frequency: Every dispatchEnsure correct material is loaded and dispatch proof is captured.
[ ] Product checked
[ ] Quantity checked
[ ] Quality checked
[ ] Vehicle number noted
[ ] Loaded vehicle photo taken
[ ] Dispatch confirmation sentProcess Code: VEHICLE_CHECK_V1
Owner: Factory Supervisor
Frequency: Weekly and before major deliveryReduce delivery failures due to vehicle issues.
[ ] Tyres checked
[ ] Fuel checked
[ ] Lights checked
[ ] Brakes checked
[ ] Driver available
[ ] Vehicle documents valid
[ ] Service due date checked
[ ] Any issue reportedInform management if vehicle is unsafe or unavailable.
Process Code: FACTORY_VISIT_V1
Owner: Sales/Factory Supervisor
Frequency: Whenever customer visits factoryGive customers a professional factory visit experience and explain product benefits clearly.
[ ] Customer welcomed
[ ] Product shown
[ ] Benefits explained
[ ] Project requirement noted
[ ] Contact details captured
[ ] Sales informed
[ ] Follow-up createdProcess Code: BILL_HANDOVER_V1
Owner: Factory Supervisor / Accounts
Frequency: Whenever purchase/expense occursEnsure all bills and expenses reach accounts correctly.
[ ] Bill collected
[ ] Photo taken
[ ] Supplier noted
[ ] Purpose noted
[ ] Amount visible
[ ] Sent to accounts
[ ] Physical copy storedProcess Code: MACHINE_SAFETY_V1
Owner: Factory Supervisor
Frequency: DailyPrevent accidents near machine and production area.
1. No hand inside danger zone during machine operation.
2. Only trained operator should handle machine.
3. Keep children/visitors away from machine.
4. Do not clean machine while it is running.
5. Report abnormal sound/vibration immediately.
6. Keep walkway clear.
7. Use basic PPE where required.[ ] Machine area clear
[ ] Operator available
[ ] No unsafe handling
[ ] Walkway clear
[ ] Cleaning done safely
[ ] Issue reported if anyProcess Code: HOUSEKEEPING_V1
Owner: Factory Supervisor
Frequency: DailyKeep factory safe, clean and easy to work in.
[ ] Walkway clear
[ ] Broken bricks removed
[ ] Tools stored
[ ] Cement protected
[ ] Machine area cleaned
[ ] Material zones neatProcess Code: ESCALATION_V1
Owner: Factory Supervisor
Frequency: Whenever issue occursEnsure critical issues are reported quickly.
Machine breakdown
High rejection
Wet/contaminated red soil
Cement shortage
Labour shortage
Customer complaint
Dispatch delay
Wrong loading
Safety incident
Vehicle breakdown
Material shortage
Quality doubtIssue:
Time:
Product/Batch:
Impact:
Photo/video:
Action already taken:
Support needed:Create a page/table called:
Date
SOP Name
Process Code
Suggested By
Current Problem
Suggested Improvement
Reason / Benefit
Photo Attached?
Priority: Low / Medium / High
Status: Open / Under Review / Approved / Rejected / Implemented
Reviewed By
Review Date
Implementation Date
Remarksflowchart TD
A[Staff suggests improvement] --> B[Supervisor reviews]
B --> C{Valid suggestion?}
C -- Yes --> D[Send to SOP owner]
C -- No --> E[Close with reason]
D --> F[Owner approves]
F --> G[Update SOP]
G --> H[Mark implemented]
Anyone can suggest. Only SOP owner or management can approve official SOP changes.
Add this section at the bottom of every SOP.
Automation Readiness
Telegram command:
n8n workflow:
Odoo object:
Approval role:
Supabase table:
Status:Example for Raw Material Receiving:
Telegram command: /soil
n8n workflow: wf_raw_material_receipt_v1
Odoo object: purchase.order / stock.picking
Approval role: Factory Supervisor
Supabase table: raw_material_receipts
Status: Future automationExample for Production Output:
Telegram command: /production
n8n workflow: wf_production_output_v1
Odoo object: mrp.production
Approval role: Factory Supervisor + QC
Supabase table: production_batches
Status: Future automationCreate Docmost groups:
Management_Admin
SOP_Editors
Supervisors
Staff_ViewersCan:
Can:
Can:
Can:
Each SOP should use:
Large title
Icon or emoji
Short purpose
Process flow diagram
Step cards
Do/Don’t table
Checklist
Photo placeholders
Escalation box
Improvement suggestion sectionUse colour meaning:
Green = Approved / Correct
Yellow = Hold / Check
Red = Reject / Stop / Escalate
Blue = Information / Record updateEvery physical-process SOP should include placeholders for real factory photos:
[PHOTO: Correct example]
[PHOTO: Wrong example]
[PHOTO: Work area]
[PHOTO: Tool/material]
[PHOTO: Final approved output]For these SOPs, create a print-friendly A4/A3 version:
Red Soil Receiving & Moisture Check
Raw Material Separation Zone
MIB 8-inch Mixing Recipe
First 20 Bricks Approval
20-Brick Mini-Stack & Sleeper Method
Visual QC / Hold / Reject
Machine Safety
Housekeeping
Loading VerificationEach poster should have:
Create a page:
Understand factory layout.
Review dashboard.
Follow Daily Opening Checklist.
Observe raw material zones.
Submit first-day observation.Focus on raw material receiving and separation.
Check red soil moisture/storage.
Suggest improvements.Focus on mixing and first 20 bricks approval.
Capture photos of correct/incorrect samples.Focus on stacking, sleepers, curing and hold/reject zones.
Standardize batch card method.Focus on dispatch planning, loading verification and vehicle checklist.Submit weekly report.
Submit SOP improvement suggestions.
Discuss with management.Create a page/template:
Week:
Supervisor:
Total production:
Top product produced:
Rejected quantity:
Main defect reason:
Raw material issues:
Machine downtime:
Labour issues:
Dispatch issues:
Customer/factory visit updates:
SOP improvement suggestions:
Support needed from management:
Photos attached:The implementation is complete when:
When creating content in Docmost:
Claude should create:
1. Complete Docmost workspace structure
2. One-stop Supervisor Dashboard
3. 20 SOP pages
4. SOP Improvement Register
5. First Week Supervisor Onboarding Plan
6. Weekly Supervisor Report Template
7. Print-friendly SOP poster sections
8. Automation mapping sections for n8n/Odoo future workflowsThe final system should make the new factory supervisor feel:
“I know what to do every morning.
I know how to control production.
I know how to check quality.
I know when to escalate.
I know where to report.
I know how to suggest improvements.”You can paste this directly into Claude and say:
“Create the full Docmost SOP workspace exactly as per this PRD. Use clean visual pages, Mermaid diagrams, tables, checklists and placeholders for real factory photos. Do not make it text-heavy.”
[1]: https://docmost.com/docs/?utm_source=chatgpt.com "Introduction | Docmost - Documentation"