The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
This sample SOP demonstrates how I document and structure a time-off request process to ensure consistency, clarity, and proper ownership across teams.
The process outlines eligibility, approval steps, and cross-functional handoffs between managers, HR, and payroll, helping reduce errors and confusion while supporting fair and timely time-off management.
I design SOPs like this to create repeatable, scalable people processes that are easy for managers and employees to follow.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Crenaly: a booking SaaS I designed and built end-to-end for appointment-based businesses in France: salons, barbers, beauty and wellness.
The core idea: when a client cancels, the freed slot is automatically offered to clients who asked for an earlier time. The first to accept gets it, their appointment moves in place, and the slot they leave is offered next. No double booking, no manual work.
Around it, a full product:
→ Branded booking page for each business, embeddable on their own site
→ Mobile-first booking flow, no account needed
→ Agenda, client management, team roles & permissions
→ Verified reviews, analytics, Stripe billing
Product, UX/UI, frontend and backend.
Next.js · TypeScript · NestJS · PostgreSQL · Redis
Automatically offering a cancelled slot to the next client is such a practical feature for salons and barbers. Designing and building Crenaly end to end must have made those flows much tighter.
Weekly Scheduling & Administrative Organisation
A one-page weekly schedule that brings every appointment together with its time, purpose and status, set in West Africa Time. It flags the one meeting still awaiting confirmation and adds an admin checklist and scheduling notes.
Understanding the Offer Lifecycle
Designing features for drivers meant going beyond individual screens and understanding how decisions unfold within a live dispatch environment.
To frame the problem, I mapped the driver decision journey across a real dispatch scenario, focusing on how offers are generated, evaluated, and confirmed under time pressure.
