Skip to content
← Back to home

Learn

Field notes

Practical guidance for building clear request and approval workflows.

Getting started

A request should have one clear path to a decision

A useful approval workflow answers four questions: what is being requested, who decides, what happens next, and where the decision is recorded. Here is how those pieces fit in Maiboro.

01Capture enough context

Start with a request type and an intake form. Ask for the information the approver actually needs: dates for time off, the resource for access, or the item and amount for a purchase. Keep the description with the request.

02Choose who decides

Configure routing rules for the people who should review a request. Review the rules against a concrete example before relying on them for daily work.

03Review and record the decision

The approver opens the request, reads the submitted details, and approves or rejects it. A decision note can explain the outcome. Delegation is available when someone else should review it.

04Keep the record connected

The request status and decision history stay with the record. Use tables and automations for the surrounding process, and inspect a workflow before activating it.

Create a workspace and explore approvals