Conceptual illustration; not a product screenshot or customer result.
Consider this illustrative purchase request. It arrives in a chat, with the quotation following by email. A manager asks for a change, and someone updates a spreadsheet. When the buyer is ready to place the order, they have to ask which version was approved.
Keep the information and decision together, with a named person responsible for what happens next. That gives the team a process it can follow without reconstructing the conversation.
Lark Approval can provide the form and approval process. Your team still needs to agree the rules, handle exceptions and act on the decision. Start with one process people already understand.
Choose a request that has a clear beginning and a decision someone is authorised to make. A purchase request is a useful example because the work continues after approval: someone must place the order and confirm it was received.
Before building the form, write down who submits the request, who decides and who carries out the approved action. Identify the person who owns the process when something goes wrong. These roles may be held by different people.
Then decide what the reviewer needs. For a purchase request, that could include the item, its purpose, the quotation, amount and currency, required date and relevant project or budget. Ask for information that supports a decision. Every extra field needs a reason to be there.
Use your organisation’s actual approval authority to decide the route. Agree how a changed item or price affects that decision. A form cannot settle an unclear spending policy.
Lark’s Approval administrator manual describes configuring forms and process steps, including what participants can read or edit. The person setting this up needs the appropriate administrative permissions. Check the requirements for your chosen setup before a rollout.
The following is an illustrative business process, not a customer case or a list of Lark’s exact status labels.
| Business stage | What happens | Who has the next action? |
|---|---|---|
| Submit | The requester provides the purpose, current quotation and required information. | The assigned reviewer. |
| Review | The reviewer checks completeness and whether the request is within their authority. | The reviewer, or the requester if information is missing. |
| Return for correction | The reviewer identifies what needs to change using the actions available in the configured process. | The requester follows the agreed correction route. |
| Decide | The authorised person approves or rejects the request. | The person responsible for the approved work, or the requester following rejection. |
| Handover | The buyer checks the approved version before placing the order. | The buyer. |
| Complete | The team records the operational result and any issue needing follow-up. | The process owner confirms closure. |
Keep the last two stages in the design. A recorded approval does not place an order, make a payment or update an accounting system by itself. Agree where the operational completion will be recorded and who keeps it current.
You may need a configured handler step or a separate work register for the handover. If your team uses Lark Base to track orders, decide how the approved request will be linked to that record. Lark Base and Lark Approval serve different purposes. Any connection between them needs to be designed and checked.
An incomplete quotation is a useful pilot case. The reviewer should explain what is missing and the requester should know how to correct it. Avoid leaving a request in limbo while the correction happens in a separate chat.
Lark allows administrators to configure whether approvers can transfer or return requests and add or remove approvers. The available actions depend on the process settings. Use the official operation-permission guidance when deciding which actions your process needs.
Also agree what happens when an approver is away. Choose an authorised cover arrangement before it is needed. Staff should not have to guess who can decide or seek informal approval elsewhere.
A changed quotation needs its own rule. Decide when the request must go through approval again, and make the version being reviewed clear. The person placing the order should be able to identify that version without reconstructing a conversation.
Take care when changing the process after launch. Lark’s Approval FAQs explain that changes to the form or process apply to new submissions. Requests already submitted retain their earlier form and process. Include in-progress requests in your change plan.
An approval project does not require an immediate move of every company document. Your team can agree where supporting files belong and check access for the people reviewing them.
For example, if a quotation remains in Google Drive, check that the assigned reviewer can open it. A link in a request is not enough when its permissions prevent a decision. Agree how the reviewed version will be retained if the working document later changes.
MatrixC uses Lark alongside Google Workspace in its daily operations. Our Lark implementation approach starts with the process your team needs to handle and the people who will use it.
Give one person responsibility for the pilot. Their job is to collect questions, resolve unclear routing and decide which changes belong in the next version.
Walk through a complete request, an incomplete one and a rejection. Include an unavailable approver and a quotation that changes. Check what each participant can see and whether the person carrying out the work receives enough context.
Once those checks are satisfactory, tell the pilot group where to submit requests and where to check progress. Agree the point at which that group stops using parallel email approvals for this process. Otherwise, people will have two routes and no shared expectation about which decision counts.
Measure what happens during ordinary use. Useful observations include requests returned for missing information, elapsed time awaiting a decision and the follow-up needed to find the current owner. Compare similar requests with the earlier process. A short pilot may reveal confusing rules before it demonstrates any time saving.
Extend the process when the participants can use it consistently and the handover works. More forms can wait.
Use this checklist to describe the process you want to improve:
MatrixC helps with Lark licensing, implementation and onboarding. Discuss your first Lark approval process and tell us your team size, the request you want to improve and how it is handled today. We can use that starting point to discuss the scope of your rollout.
Assess Qwen for a defined business application. Understand model access, task fit, evaluation, costs and…
Compare managed Qwen access and selected model weights. Check serving costs, model terms, control, failures…
Estimate Qwen input and output charges, then add retries, review and operations. Use a dated…
Design an English and Bahasa Malaysia Qwen evaluation with varied cases, human grading, acceptance rules…
Map Qwen access, inference, storage and retention for the exact service. Prepare deployment questions about…
Prepare a Qwen pilot brief with the task, permitted data, acceptance rules, budget and deployment…