One place to find, review and approve your workers' skills.

1. Read the month's sales and purchase records.
2. Match invoices to the figures in the books.
3. List mismatches and missing invoices.
4. A person reviews the pack and files the return.

Needs from you: Sales and purchase records for the month; Books or an accounting export.

What it needs connected: Accounting export file; GST return data, read only.

Where a person is designed to decide: A person reviews the pack and files the return.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Find invoices past their due date.
2. Draft a reminder for each customer, in their language.
3. Queue the drafts for approval.
4. A person approves, then the reminder goes out.
5. Note the reply against the invoice.

Needs from you: Open invoices with due dates; Customer contact details.

What it needs connected: Accounting export file; Email or WhatsApp.

Where a person is designed to decide: A person approves, then the reminder goes out.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI, WhatsApp, Hindi and regional.

1. Read leave requests and attendance records.
2. Count balances and flag clashes.
3. Write a short summary for the manager.

Needs from you: Leave requests; Attendance records.

What it needs connected: HR records, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read each new enquiry.
2. Score it against the buyer you want.
3. Suggest the next step and who should take it.
4. A person decides which leads to pursue.

Needs from you: New enquiries; A short description of your best-fit customer.

What it needs connected: Enquiry inbox or form.

Where a person is designed to decide: A person decides which leads to pursue.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. List quotes with no reply after a set number of days.
2. Draft a short follow-up for each.
3. A person approves the wording.
4. Send it and record the reply.

Needs from you: Open quotes and their dates; Contact details.

What it needs connected: Email or WhatsApp.

Where a person is designed to decide: A person approves the wording.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, WhatsApp.

1. Read the incoming request in whatever language it arrives.
2. Label the topic and how urgent it is.
3. Draft a first reply for a person to edit.
4. A person sends the reply.

Needs from you: Incoming support requests; Your common answers.

What it needs connected: Support inbox.

Where a person is designed to decide: A person sends the reply.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. Read the open pull requests and their check results.
2. Group them by what is ready, failing or waiting.
3. Write the summary for the team.

Needs from you: Repository pull requests; Check results.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Take a topic from your calendar.
2. Draft the post for each channel.
3. Check it against your brand and claims rules.
4. A person approves.
5. Schedule it for publishing.

Needs from you: A topic or calendar entry; Your tone and claims rules.

What it needs connected: Publishing channel.

Where a person is designed to decide: A person approves.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the customer list and the consent records.
2. Find records with no consent or an expired one.
3. Report the gaps by source.

Needs from you: Customer list; Consent records.

What it needs connected: Customer records, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Note each approval, report and record as it is made.
2. File it with its date and who approved it.
3. Build the folder an auditor asks for.
4. A person checks it before it is shared.

Needs from you: Approvals and reports from your workspace.

What it needs connected: Workspace activity log.

Where a person is designed to decide: A person checks it before it is shared.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Collect the approvals waiting and the messages that need a reply.
2. Rank them by urgency.
3. Write the brief with a link to each item.

Needs from you: Approvals waiting; Messages and tasks.

What it needs connected: Workspace approvals.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the week's invoices, payments and tasks.
2. Compare them with last week.
3. Write the page with three things to act on.
4. A person reads it and picks what to do.

Needs from you: Invoices and payments; Task list.

What it needs connected: Accounting export file.

Where a person is designed to decide: A person reads it and picks what to do.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the bank or card lines for the period.
2. Clean up vendor names and remove duplicate lines.
3. Assign each line to a category you defined.
4. A person reviews the odd ones and accepts the result.

Needs from you: Bank or card statement lines; Your list of expense categories.

What it needs connected: Bank statement export.

Where a person is designed to decide: A person reviews the odd ones and accepts the result.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the GST invoice records and the UPI statement.
2. Match each payment to an invoice by amount, date and reference.
3. List what matched and what did not.
4. A person resolves the unmatched items.

Needs from you: GST invoice records; UPI payment statement.

What it needs connected: Accounting export file; UPI statement file.

Where a person is designed to decide: A person resolves the unmatched items.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the bank balance and the receivables due.
2. List known payments, including payroll and tax dates.
3. Project cash week by week for 13 weeks.
4. Mark the weeks where cash runs low.

Needs from you: Bank balance; Receivables and payables with dates; Payroll dates.

What it needs connected: Bank statement export; Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Watch the mailbox for supplier invoices.
2. Pull out the supplier, number, date and amount.
3. Check against the payables log for duplicates.
4. A person approves each invoice for payment.
5. Record it in the payables log.

Needs from you: A mailbox for supplier invoices; Your payables log.

What it needs connected: Email inbox; Accounting export file.

Where a person is designed to decide: A person approves each invoice for payment.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the payroll report and the ledger accounts.
2. Compare each head of pay and deduction.
3. List the differences with the amounts.
4. A person decides what to correct.

Needs from you: Payroll report; Ledger accounts for payroll.

What it needs connected: Accounting export file; Payroll report file.

Where a person is designed to decide: A person decides what to correct.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Collect the client details and what was sold.
2. Work out the tax lines.
3. Draft the numbered invoice.
4. A person approves it.
5. Send it and track it until paid.

Needs from you: Client details; What was sold and at what rate.

What it needs connected: Accounting export file; Email.

Where a person is designed to decide: A person approves it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the spend lines for the last few months.
2. Spot recurring charges and costs that crept up.
3. Rank them by the saving if cut.
4. Write a short list for a person to decide on.

Needs from you: Spend lines for the period.

What it needs connected: Bank statement export.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Ask a few questions about how your team spends.
2. Draft the policy in plain language.
3. List the limits and the approvals it sets.
4. A person edits and adopts it.

Needs from you: Answers about how your team spends.

Where a person is designed to decide: A person edits and adopts it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the role and the joining date.
2. List what the person must learn and receive.
3. Assign an owner and a date to each item.
4. A manager reviews and shares the plan.

Needs from you: Role and joining date; Your onboarding checklist.

Where a person is designed to decide: A manager reviews and shares the plan.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the job description.
2. Draft questions for each skill that matters.
3. Add scoring points and a note template.
4. A person edits the kit before it is used.

Needs from you: Job description.

Where a person is designed to decide: A person edits the kit before it is used.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the job description and the resumes.
2. Compare each resume with the requirements.
3. Rank them and show the gaps, with the reason.
4. A person decides who moves on.

Needs from you: Job description; Resumes.

What it needs connected: Resume folder.

Where a person is designed to decide: A person decides who moves on.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP, Hindi and regional.

1. Read the contact list.
2. Standardise names, phone numbers and emails.
3. Find likely duplicate contacts.
4. A person approves each merge.

Needs from you: Contact list.

What it needs connected: CRM export file.

Where a person is designed to decide: A person approves each merge.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, DPDP.

1. Read the scope sheet and your template.
2. Fill in scope, pricing and terms.
3. Check the figures against your rate card.
4. A person reviews and sends it.

Needs from you: Scope sheet; Proposal template; Rate card.

Where a person is designed to decide: A person reviews and sends it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the request and list every requirement.
2. Draft an answer for each one from your own material.
3. Add pricing and risk notes.
4. A person reviews before anything is submitted.

Needs from you: The request document; Your past answers and rate card.

Where a person is designed to decide: A person reviews before anything is submitted.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the raw notes.
2. Pull out what was decided and promised.
3. List the open questions and who owns them.

Needs from you: Raw call notes.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Collect the unanswered reviews.
2. Draft a reply to each, matching its tone.
3. Flag the ones that need a person's judgment.
4. A person posts the replies.

Needs from you: Unanswered reviews; Your tone guide.

What it needs connected: App store reviews.

Where a person is designed to decide: A person posts the replies.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read each ticket.
2. Classify it by topic and urgency.
3. Suggest a reply from your approved answers.
4. Route urgent or unusual tickets to a named person.

Needs from you: Incoming tickets; Approved answers; Escalation rules.

What it needs connected: Support inbox.

Where a person is designed to decide: Route urgent or unusual tickets to a named person.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. Read the ticket, logs and screenshots.
2. Write the steps to reproduce.
3. Note what was expected and what happened.
4. A person files the report.

Needs from you: Support ticket; Logs or screenshots.

What it needs connected: Support inbox.

Where a person is designed to decide: A person files the report.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read your policies and past tickets.
2. Group the common questions.
3. Draft a flow for each group.
4. A person approves the flows.

Needs from you: Support policies; Past tickets.

Where a person is designed to decide: A person approves the flows.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the week's work items and changes.
2. Group them by shipped, in progress and blocked.
3. Write the report for the team lead.

Needs from you: Work items; Change history.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the week's change history.
2. Spot patterns such as rework and long reviews.
3. Write the retrospective with one suggestion.

Needs from you: Change history.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the change and its description.
2. Write criteria that can be checked.
3. List the manual steps and the evidence for each.
4. A person confirms the plan.

Needs from you: Change description.

Where a person is designed to decide: A person confirms the plan.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the change.
2. Find the pages that describe what changed.
3. List the ones that are now wrong.
4. A person updates them.

Needs from you: Change history; Documentation pages.

What it needs connected: Code host, read only.

Where a person is designed to decide: A person updates them.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the design and its goal.
2. Check clarity, hierarchy and accessibility.
3. List the issues in priority order.

Needs from you: The design and its goal.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read your goals and the dates that matter.
2. Propose topics for each week.
3. Assign an owner and a channel to each.
4. A person approves the calendar.

Needs from you: Goals; Key dates and festivals.

Where a person is designed to decide: A person approves the calendar.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the brief and the links.
2. Fill your newsletter template.
3. Check the send rules.
4. A person approves the send.

Needs from you: Issue brief; Links; Newsletter template.

What it needs connected: Email sender.

Where a person is designed to decide: A person approves the send.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the editorial calendar.
2. Adapt each topic for each platform.
3. Suggest times and tags.
4. A person approves before anything is scheduled.

Needs from you: Editorial calendar; Platform list.

What it needs connected: Publishing channel.

Where a person is designed to decide: A person approves before anything is scheduled.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the list of changes.
2. Write the announcement leading with user impact.
3. Add the upgrade steps.
4. A person approves it.

Needs from you: List of changes.

Where a person is designed to decide: A person approves it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the text and your term list.
2. Rewrite it in plain sentences.
3. Show the changes next to the original.
4. A person accepts or edits.

Needs from you: The text; Terms to keep.

Where a person is designed to decide: A person accepts or edits.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the feeds you listed.
2. Pick the new posts that matter to you.
3. Write a short note with links.

Needs from you: Feeds and blogs you follow.

What it needs connected: Public feeds.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the filings your business has.
2. Place each due date on the calendar.
3. Remind the owner before each date.
4. A person confirms each filing is done.

Needs from you: List of your filings; Your financial year.

Where a person is designed to decide: A person confirms each filing is done.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, DPDP.

1. List the rules that apply to your business.
2. Match each rule to a control you run.
3. Note the evidence that proves it.
4. A person reviews the gaps.

Needs from you: Rules that apply; Your current controls.

Where a person is designed to decide: A person reviews the gaps.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the raw notes.
2. Write the decisions made.
3. List each action with an owner and a date.
4. A person confirms the list.

Needs from you: Meeting notes.

Where a person is designed to decide: A person confirms the list.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the updates from the team.
2. Pick what needs action first.
3. Write the summary with that at the top.

Needs from you: Team updates.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read new payments and milestones.
2. Add them to the ledger.
3. Show the running total and the next milestone.

Needs from you: Payments received; Milestone list.

What it needs connected: Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read the document or transcript.
2. Pull out the key points.
3. Write a short summary with page or time references.

Needs from you: The document, link or recording.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the open work and the goals.
2. Pick the top three priorities.
3. Write the next useful task for each.
4. A person confirms the priorities.

Needs from you: Open work; Goals.

Where a person is designed to decide: A person confirms the priorities.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Collect the approvals waiting in your workspace.
2. Sort them by how long they have waited.
3. Send the digest to the owner.

Needs from you: Approvals waiting.

What it needs connected: Workspace approvals.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the content calendar and the draft status.
2. Pick the drafts to write next.
3. List the posts that are blocked and why.
4. A person confirms the picks.

Needs from you: Content calendar.

Where a person is designed to decide: A person confirms the picks.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the week's work items.
2. Find the ones with no movement.
3. Write the note for the team lead.

Needs from you: Work items.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read open invoices and their due dates.
2. Rank by amount and days overdue.
3. Draft a reminder for the longest overdue.
4. A person approves the drafts.

Needs from you: Open invoices.

What it needs connected: Accounting export file.

Where a person is designed to decide: A person approves the drafts.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the month's sales and purchase records.
2. Check for missing invoices and mismatched figures.
3. List what to fix before the return date.
4. A person confirms it is ready.

Needs from you: Sales and purchase records.

What it needs connected: Accounting export file.

Where a person is designed to decide: A person confirms it is ready.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the month's spend lines.
2. Compare with the month before.
3. Write the short review with the three biggest changes.

Needs from you: Spend lines.

What it needs connected: Bank statement export.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read the deal list and last contact dates.
2. Find the deals with no movement.
3. Write the review with a next step for each.

Needs from you: Deal list.

What it needs connected: CRM export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp.

1. Read the open tickets.
2. Find the oldest and the most repeated topics.
3. Write the review for the support lead.

Needs from you: Open tickets.

What it needs connected: Support inbox.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the list of users and their access.
2. Flag access that looks unused or too broad.
3. A person confirms or removes each item.

Needs from you: List of users and access.

What it needs connected: Workspace users.

Where a person is designed to decide: A person confirms or removes each item.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the customer list and the consent records.
2. Find records with no consent or an expired one.
3. Report the gaps by source.

Needs from you: Customer list; Consent records.

What it needs connected: Customer records, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read approved leave.
2. Find days where too few people are in.
3. Write the outlook for managers.

Needs from you: Approved leave.

What it needs connected: HR records, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Draft the tax invoice from the sale.
2. A person approves and the invoice is sent.
3. Track it until the due date.
4. Draft a reminder if it is late and a person approves it.
5. Match the payment and close the invoice.

Needs from you: The sale; Client details.

What it needs connected: Accounting export file; Email or WhatsApp.

Where a person is designed to decide: A person approves and the invoice is sent.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI, WhatsApp.

1. Collect the month's sales and purchase records.
2. Match invoices and list mismatches.
3. Fix or explain each mismatch.
4. Prepare the return pack.
5. A person reviews and files the return.

Needs from you: Sales and purchase records.

What it needs connected: Accounting export file; GST return data, read only.

Where a person is designed to decide: A person reviews and files the return.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the claim and its receipts.
2. Check it against the expense policy.
3. A manager approves or rejects it.
4. A person makes the payment.
5. Record it in the books.

Needs from you: Claim and receipts; Expense policy.

What it needs connected: Accounting export file.

Where a person is designed to decide: A person makes the payment.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read the enquiry and score its fit.
2. A person decides whether to pursue it.
3. Draft the proposal from your template.
4. A person reviews and sends it.
5. Set a follow-up for a few days later.

Needs from you: Enquiry; Proposal template.

What it needs connected: Enquiry inbox or form; Email or WhatsApp.

Where a person is designed to decide: A person reviews and sends it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, GST.

1. Read the message and label topic and urgency.
2. Draft a reply from your approved answers.
3. A person edits and sends the reply.
4. Escalate to a named person if it is unusual.
5. Close the ticket when the customer confirms.

Needs from you: Customer message; Approved answers.

What it needs connected: Support inbox.

Where a person is designed to decide: A person edits and sends the reply.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. Create the onboarding checklist for the role.
2. A manager approves the plan.
3. Collect the joiner's documents.
4. Schedule the first-week sessions.
5. Check in at 30 days.

Needs from you: Offer details; Onboarding checklist.

Where a person is designed to decide: A manager approves the plan.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Take the idea from your calendar.
2. Draft the post for each channel.
3. Check it against your brand and claims rules.
4. A person approves it.
5. Schedule and publish it, then note the result.

Needs from you: Idea; Brand and claims rules.

What it needs connected: Publishing channel.

Where a person is designed to decide: A person approves it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Write the acceptance criteria for the change.
2. Build the change in its own branch.
3. A second reviewer checks it.
4. Open the pull request with the evidence.
5. The owner releases it.

Needs from you: Change request.

What it needs connected: Code host.

Where a person is designed to decide: The owner releases it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Send the consent request in the person's language.
2. Record the answer with its date and source.
3. Show the record to the owner on request.
4. A person handles any withdrawal or erasure request.

Needs from you: Person's contact details; Purpose of use.

What it needs connected: Email or WhatsApp; Customer records.

Where a person is designed to decide: A person handles any withdrawal or erasure request.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP, WhatsApp, Hindi and regional.

1. Collect invoices, payments and tasks for the month.
2. Reconcile the main accounts.
3. Write the one-page summary.
4. The owner reads it and signs off.

Needs from you: Invoices and payments; Task list.

What it needs connected: Accounting export file.

Where a person is designed to decide: The owner reads it and signs off.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the deductions recorded this month.
2. Add them up by section.
3. Send the amounts and the due date to the finance owner.

Needs from you: Deduction records.

What it needs connected: Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the submitted claims and receipts.
2. Compare each claim with the expense policy.
3. Flag claims that break the policy.
4. A person approves or returns each claim.

Needs from you: Expense claims; Expense policy.

What it needs connected: Expense claim file.

Where a person is designed to decide: A person approves or returns each claim.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Collect vendor bills due this week.
2. Check each against its purchase record.
3. List the payments in a batch.
4. A person approves the batch.
5. Record the approved batch for the books.

Needs from you: Vendor bills; Purchase records.

What it needs connected: Accounting export file; Bank statement export.

Where a person is designed to decide: A person approves the batch.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read the notice.
2. Note the reply deadline and the issue raised.
3. List the documents the reply will need.
4. A person decides how to respond.

Needs from you: The notice.

What it needs connected: Email inbox.

Where a person is designed to decide: A person decides how to respond.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read open invoices and bills.
2. Place each on its due date.
3. Write the outlook with the biggest gaps first.

Needs from you: Open invoices; Open bills.

What it needs connected: Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the agreed role, pay and start date.
2. Fill the company's offer template.
3. A person checks and signs off the letter.

Needs from you: Agreed terms; Offer template.

What it needs connected: HR records, read only.

Where a person is designed to decide: A person checks and signs off the letter.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the open roles and the panel's free times.
2. Propose slots to the candidate.
3. A person confirms the slot.
4. Send the invite to everyone.
5. Note the interview in the hiring tracker.

Needs from you: Panel availability; Candidate list.

What it needs connected: Email; Resume folder.

Where a person is designed to decide: A person confirms the slot.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read leave balances.
2. Pick people above the limit set by HR.
3. Draft the nudge for HR to send.

Needs from you: Leave records.

What it needs connected: HR records, read only.

Where a person is designed to decide: Draft the nudge for HR to send.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Open the checklist when the notice is logged.
2. List accounts and assets to recover.
3. A person confirms each item is done.
4. Prepare the dues summary for payroll.
5. Close the checklist.

Needs from you: Exit notice; Asset list.

What it needs connected: Workspace users; HR records, read only.

Where a person is designed to decide: Prepare the dues summary for payroll.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the leads and deals.
2. Group them by source.
3. Write the report with the clearest differences first.

Needs from you: Lead and deal records.

What it needs connected: CRM export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Find quotes with no reply.
2. Draft a short follow-up for each.
3. A person approves the messages.

Needs from you: Quotes sent.

What it needs connected: CRM export file; Email or WhatsApp.

Where a person is designed to decide: A person approves the messages.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp.

1. List contracts ending in the next 60 days.
2. Draft a renewal note for each.
3. A person approves the notes.
4. Send them.
5. Log replies in the CRM.

Needs from you: Contract end dates; Client details.

What it needs connected: CRM export file; Email.

Where a person is designed to decide: A person approves the notes.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the enquiry and the notes from the call.
2. Fill the standard proposal outline.
3. A person edits and sends it.

Needs from you: Enquiry; Call notes.

What it needs connected: Enquiry inbox or form.

Where a person is designed to decide: A person edits and sends it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the open tickets.
2. Group them by age and topic.
3. Send the summary to the support lead.

Needs from you: Open tickets.

What it needs connected: Support inbox.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the request and the order.
2. Check it against the refund policy.
3. Draft the reply.
4. A person approves the refund and the reply.
5. Record the outcome.

Needs from you: Refund request; Order record.

What it needs connected: Support inbox; Customer records, read only.

Where a person is designed to decide: A person approves the refund and the reply.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read recent tickets.
2. Find repeated questions.
3. Check each against the help articles.
4. List the gaps.

Needs from you: Recent tickets; Help articles.

What it needs connected: Support inbox.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Read the customer's message.
2. Draft the reply in the same language.
3. The agent checks the wording and sends it.

Needs from you: Customer message.

What it needs connected: Support inbox.

Where a person is designed to decide: The agent checks the wording and sends it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional, WhatsApp.

1. Read the changes in the release.
2. Group them by what users notice.
3. A person edits and publishes the notes.

Needs from you: Change list.

What it needs connected: Code host, read only.

Where a person is designed to decide: A person edits and publishes the notes.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the dependency list.
2. Check each for newer versions.
3. Write the list with the riskiest first.

Needs from you: Dependency list.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Collect the alerts and messages from the incident.
2. Build the timeline.
3. Draft the write-up and follow-ups.
4. A person reviews and signs it off.

Needs from you: Alerts; Incident chat.

What it needs connected: Workspace activity log.

Where a person is designed to decide: A person reviews and signs it off.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the pull request.
2. List missing tests and notes.
3. Post the checklist for the author.

Needs from you: Pull request.

What it needs connected: Code host.

Where a person is designed to decide: Post the checklist for the author.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read your themes and key dates.
2. Spread topics across the month.
3. A person edits the calendar.

Needs from you: Themes; Key dates.

What it needs connected: Publishing channel.

Where a person is designed to decide: A person edits the calendar.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: Hindi and regional.

1. Pick the festival and the offer.
2. Draft the posts and messages.
3. A person approves them.
4. Schedule the posts.
5. Collect results after the festival.

Needs from you: Festival; Offer.

What it needs connected: Publishing channel; Email or WhatsApp.

Where a person is designed to decide: A person approves them.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. Collect new reviews.
2. Draft a reply to each.
3. A person approves and posts the replies.

Needs from you: New reviews.

What it needs connected: App store reviews.

Where a person is designed to decide: A person approves and posts the replies.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the page.
2. Check titles, headings and links.
3. List the fixes, most useful first.

Needs from you: Page address.

What it needs connected: Public feeds.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. List the places that collect personal data.
2. Check each has a purpose and a consent line.
3. List the gaps for a person to fix.

Needs from you: Data collection points.

What it needs connected: Workspace activity log.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the policy register.
2. Find policies due within 30 days.
3. Send the list to the policy owners.

Needs from you: Policy register.

What it needs connected: Workspace approvals.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Send the questionnaire to the vendor.
2. Track the reply date.
3. Summarise the answers.
4. A person scores the vendor.
5. File the result.

Needs from you: Vendor list; Questionnaire.

What it needs connected: Email.

Where a person is designed to decide: A person scores the vendor.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: DPDP.

1. Read the auditor's request list.
2. Find each document in your records.
3. Put them in one folder with a source note.
4. A person checks the folder.

Needs from you: Request list; Records.

What it needs connected: Workspace activity log.

Where a person is designed to decide: A person checks the folder.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read this month's numbers and notes.
2. Draft the update.
3. The founder edits and sends it.

Needs from you: Monthly numbers; Notes.

What it needs connected: Accounting export file.

Where a person is designed to decide: The founder edits and sends it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the week's figures from each area.
2. Write one page with the changes that matter.
3. Send it to the founder.

Needs from you: Weekly figures.

What it needs connected: Workspace activity log; Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Log the approved role.
2. Track candidates for the role.
3. A person approves each stage.
4. Update the plan after each stage.
5. Close the role at offer.

Needs from you: Approved roles.

What it needs connected: Resume folder.

Where a person is designed to decide: A person approves each stage.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Collect the monthly reports.
2. Assemble them in the board format.
3. A person reviews the pack.
4. Send the pack.
5. Log actions from the meeting.

Needs from you: Monthly reports.

What it needs connected: Email.

Where a person is designed to decide: A person reviews the pack.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the meeting notes.
2. List the decisions made.
3. Record each with an owner and a reason.

Needs from you: Meeting notes.

What it needs connected: Workspace activity log.

Where a person is designed to decide: Record each with an owner and a reason.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read each quote.
2. Line up the items and terms.
3. Write the comparison with the clearest saving first.

Needs from you: Supplier quotes.

What it needs connected: Email inbox.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Open the checklist when the customer signs up.
2. Send the welcome steps.
3. A person confirms setup is complete.
4. Check in after a week.
5. Close the checklist.

Needs from you: New customer record.

What it needs connected: Customer records; Email or WhatsApp.

Where a person is designed to decide: A person confirms setup is complete.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp.

1. Read attendance and changes for the month.
2. Look for missing or odd entries.
3. List them for a person to resolve.

Needs from you: Attendance; Pay changes.

What it needs connected: Payroll report file.

Where a person is designed to decide: List them for a person to resolve.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the invoice.
2. Check the required details are present.
3. List what is missing.

Needs from you: Invoice.

What it needs connected: Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.