What Can I Build?
Patterns and examples to help you decide what to build — from simple daily logs to multi-person decision protocols.
Maps range from a personal three-stage log you run every morning to a multi-role approval chain that routes work across departments. This page organizes what you can build into patterns — recurring shapes that combine stages, blocks, roles, and transitions in a recognizable way.
Each pattern highlights the Eddy features that drive it, a builder tier so you know what skills are involved, and a handful of concrete examples across different domains. Where a ready-made template exists, it is linked.
Patterns are not exclusive. A "content delivery + sign-off" Map is really just patterns 2 and 3 combined. Start with the shape that matches your need, then layer in more as you learn.
Where to start
Patterns 1–4 work well for solo builders or small teams with a single role. Patterns 5–8 shine when you have multiple people and handoffs. If you are new to building, start with Your First Map and come back here for inspiration.
1. Structured logging and tracking
Run it daily, weekly, or whenever something happens. Each submission adds a row to a sheet — the sheet becomes the log.
Builder tier: Foundational Key features: Repeatable start links, input blocks (date, number, text, attachment), sheets
Example ideas:
- Daily pet care log — feeding times, meds, toileting notes
- Weekly grocery or meal planning order
- Expense or petty cash log
- Vehicle mileage or equipment maintenance log
- Timesheet or hours tracking
- Habit tracker — exercise, reading, meditation
- Meeting notes log
- Inventory count or stock check
Template: Data Collection covers the basic intake-and-review shape.
2. Content delivery and media sharing
Present material — video, files, rich text — and optionally collect acknowledgment or feedback at the end.
Builder tier: Foundational Key features: Content blocks (rich text, video, resource, image gallery), attachment blocks
Example ideas:
- Design asset review — share mockups or exports, collect structured feedback
- Training module or learning path — video followed by comprehension inputs
- Policy or SOP distribution with read-acknowledgment
- Product demo walkthrough
- Meeting recording distribution with action item capture
- Announcement or newsletter with confirmation
3. Accountability and sign-off
Work through a checklist or task list, then sign off that it is done. The sheet records who completed what, when.
Builder tier: Foundational Key features: Checklist and todo blocks, checkbox blocks, discussion blocks, review blocks
Example ideas:
- Daily opening or closing checklist — hospitality, retail, construction site
- Safety inspection or pre-shift check
- Compliance attestation — "I confirm I have read and understood…"
- Code review or QA sign-off
- Audit preparation checklist
- Shift handover checklist
- Monthly reconciliation sign-off
4. Collection and survey
Share a start link, each person fills in a form (one submission per person), and the sheet aggregates all responses.
Builder tier: Foundational Key features: Single-session start links (one per user), required fields, select and multi-select blocks
Example ideas:
- Team pulse survey or check-in
- Customer or client feedback form
- Event RSVP with preferences — dietary, accessibility, session choices
- Retrospective input collection
- Skills or interest inventory
- Contact information gathering
- Research questionnaire or intake form
Template: Data Collection can be configured for one-submission-per-person intake.
5. Request and approval
A requester submits, an approver reviews and decides, and the path branches based on the decision.
Builder tier: Intermediate — requires multiple roles and conditional transitions Key features: Multiple Map Roles (Requester, Approver), conditional transitions, select blocks, review blocks
Example ideas:
- Leave or time-off request
- Purchase order or expense approval
- IT access request
- Budget or spending approval
- Content publishing approval
- Vendor or supplier onboarding
- Discount or pricing exception
6. Multi-stage handoff
Person A does their part, hands off to Person B, Person C finalizes. Each role sees only the stages assigned to them.
Builder tier: Intermediate — requires multiple roles and stage-level permissions
Key features: Multiple Map Roles, stage assignments with can_write and can_progress, automatic notifications, sequential transitions
Example ideas:
- Employee onboarding — new hire fills in details, IT provisions accounts, HR completes checks, manager reviews
- Client onboarding — sales hands off to operations, operations hands off to account manager
- Incident response — reporter logs the incident, investigator reviews, manager approves resolution
- Creative workflow — brief submitted, designer produces work, reviewer approves or requests revision
- Hiring pipeline — application received, phone screen, interview, offer
Template: Onboarding demonstrates a four-role handoff across departments.
7. Decision and triage protocols
Gather structured input, evaluate against criteria, and route to different outcomes based on what was entered.
Builder tier: Advanced — requires conditional transition rules evaluated against sheet data and branching graph paths Key features: Conditional transitions with rule builder, select blocks driving branching, multiple outgoing transitions from a single stage
Example ideas:
- Risk assessment — severity rating determines escalation path
- Support ticket triage and routing
- Return or refund processing — reason determines resolution procedure
- Diagnostic flowchart — symptoms route to recommended actions
- Incident severity classification and response protocol
Template: Task Delegation demonstrates conditional loops and an approve-or-revise branching gate.
8. Collaborative deliberation
Propose something, discuss it as a group, poll or vote, and record the outcome.
Builder tier: Intermediate to Advanced — uses discussion blocks, polls, and optionally per-participant stages Key features: Discussion blocks, poll blocks (with live tally), content blocks for context-setting, review blocks for surfacing outcomes
Example ideas:
- Team decision-making — propose options, discuss trade-offs, vote
- Committee or board review
- Design critique session — structured criteria, threaded discussion, coordinator sign-off
- Retrospective discussion with action item voting
- Policy consultation round
Template: Feedback Process demonstrates structured critique with coordinator approval and shared results.
Combining patterns
Most real Maps combine two or more patterns. A few combinations that work well together:
| Combination | What it looks like |
|---|---|
| Logging + sign-off (1 + 3) | A daily checklist that also captures freeform notes — the sheet records both the checks and the commentary |
| Content delivery + collection (2 + 4) | A training video followed by a quiz or feedback form — the sheet captures responses per viewer |
| Request + handoff (5 + 6) | A purchase request that, once approved, triggers IT procurement and finance processing in sequence |
| Collection + deliberation (4 + 8) | Gather retrospective input from the team individually, then discuss and vote on priorities together |
| Handoff + decision protocol (6 + 7) | An incident report that routes through investigation, classification, and resolution — each handled by a different role, with conditional paths at key decision points |
Builder tiers at a glance
The builder tiers referenced above correspond to the skills you develop as you learn the builder:
| Tier | What it means | Patterns |
|---|---|---|
| Foundational | Linear stages, single role, basic input and content blocks, start links | 1, 2, 3, 4 |
| Intermediate | Branching, multiple roles with handovers, discussion and review blocks, polls | 5, 6, 8 |
| Advanced | Conditional transition rules against sheet data, looping workflows, section visibility rules | 7 |
You do not need to master everything at once. Most users develop strength in one area first — the tier is a rough guide, not a gate.
What is not listed here
This page covers patterns you can build today. A few areas are under active development:
- Process Intelligence — richer reporting on how Sessions perform over time, beyond the current Operator view
- Embedded workflows — launching a sub-Map from within a Session, useful for nested processes
- AI blocks — summarize, critique, or expand text within a stage using your own API key
As these features mature, new patterns will emerge. If you build something interesting that is not listed here, the patterns on this page are not exhaustive — they are starting points.