Skip to main content
GullySystem
Professional services

Workflow and Approvals for Vaastu consultants

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

Configure the review of draft observations and advice before the practice shares them with the client. A junior's mark-up, the senior consultant's review and the final issued letter are separate states. The workflow records who authorised communication; it does not validate the recommendations or replace engineering, legal or other professional judgement.

Bring the records the workflow depends on.

  • Consultation reference and the draft advice with its supporting plan revision.
  • Named reviewer, issue authority and any permitted delegation within the practice.
  • Client comments, revision reasons and the conditions for final external issue.

Outputs to check

  • Review record identifying requested corrections and the person approving the issue version.
  • Issued-advice history linking the final letter to its approved draft and recipients.

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Preparing consultant

Submits the draft and its supporting documents, responding to review comments without bypassing the issue decision.

Senior approver

Accepts, returns or declines the proposed issue and records the scope of the approval.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Draft changed after approval

Return the changed material for the required review instead of carrying the earlier approval onto new wording.

Approver unavailable

Use an authorised delegate if the practice permits one; an unassigned task is not permission for the author to self-approve.

Urgent client request

Keep the issue control intact and record the escalation rather than sending an unreviewed draft as final advice.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • An externally issued letter is linked to an approved version and its named approver.
  • Changing the supporting plan or substantive recommendation triggers the configured review requirement.
  • A preparing user cannot mark their own draft approved unless an explicit authority rule permits that action.
Vaastu consultants

How the business operates.

Vaastu work is personal, and it repeats. A family consults before buying a plot, returns before construction, and again years later when a son sets up an office in another city.

Client and property file

Keep each client’s properties, floor plans by version, and your advice on each in date order, so the third consultation starts where the second ended.

Appointment booking with fee

Book plan reviews and site visits, collect the fee by QR code or card, and send a receipt. Booking is added to the project file during implementation.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client and property identifier
  • Floor-plan version and source
  • Visit observations, photographs and advisory note
  • Recommendation, client response and later revision

Operational bottlenecks to check

The old plan is lost

The layout changes, and the first version you reviewed sat in a phone that was sold last year. The client remembers it differently.

Advice differs between visits

With no record, the second consultation can contradict the first, and the client notices and says so. Confidence in the advice drops.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Record the brief

    Identify the property, consultation format and material the client supplies. Keep each plan version with its source and date.

  2. 2. Arrange the consultation

    Book the agreed review or visit and record the commercial scope. A changed appointment remains distinguishable from a new consultation.

  3. 3. Document the advice

    Attach the consultant’s observations and recommendations to the relevant property and plan version. Retain what was actually shared with the client.

  4. 4. Handle a revised plan

    Record the new plan, requested changes and consultation round. Compare it with the preceding advice and apply the agreed revision-fee arrangement.

  5. 5. Close and follow up

    Record the client’s response, documents issued and payment position. Use agreed follow-up dates without treating a recommendation as a verified result.

Industry reports to connect with

  • Appointments and property files awaiting documents
  • Open recommendation and revision rounds
  • Consultation fees and receipts outstanding
  • Referral sources and returning client requests

Questions before implementation.

When should vaastu consultants consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Consultation reference and the draft advice with its supporting plan revision.; Named reviewer, issue authority and any permitted delegation within the practice.; Client comments, revision reasons and the conditions for final external issue. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. An externally issued letter is linked to an approved version and its named approver. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements