Skip to main content
GullySystem
Professional services

Project Timelines with Gantt Charts for Vaastu consultants

Show project tasks, dependencies and milestones on a calendar.

Project Management

Does this function belong in your operation?

Use when project stages depend on one another and delays affect later work.

A project plan is created or its dates change.

A consultation schedule can run from receipt of plans to a site visit, draft advice, senior review and final issue. Use dependencies that reflect this work instead of importing a construction programme. A delay to plan receipt or access to the property should expose the affected report milestone without implying that the software sets the consultant's conclusion.

Bring the records the workflow depends on.

  • Consultation stages with their owner and planned completion dates.
  • Required plan and access prerequisites, client review points and the final issue milestone.
  • Consultant working calendars and the approved rule for changing commitments.

Outputs to check

  • Consultation timeline showing prerequisites, active stages and the next client-facing milestone.
  • Change record explaining why a date moved and which later tasks were affected.

Follow the project timelines with gantt charts workflow.

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

  1. 1. List the work

    Define tasks, milestones and expected durations.

  2. 2. Set dependencies

    Identify prerequisites and the applicable work calendar.

  3. 3. Review the baseline

    Check dates with task and resource owners before approval.

  4. 4. Update progress

    Record actual starts, completions and authorised changes.

  5. 5. Review impact

    Show downstream effects and communicate the revised plan to affected owners.

Who uses the module, and who approves?

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

Practice scheduler

Maintains the plan and obtains the owner's confirmation before changing an external commitment.

Responsible consultant

Confirms stage completion and whether enough information exists to start the next review activity.

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.

Site access postponed

Move the visit through an approved change and identify any draft work that genuinely depends on the visit.

Revised floor plan received

Ask the consultant whether additional study is needed; a file upload must not automatically mark the review complete.

Client comments remain open

Keep the final issue milestone awaiting the required response rather than completing it because the planned date has passed.

Can this work independently?

Timelines can be planned independently with tasks, durations and calendars. Resource allocation confirms capacity, procurement supplies delivery dependencies, and progress updates come from work owners. A date displayed on the chart is a plan until the relevant owner confirms completion.

Systems and records it connects with

  • Task management: Assigned work, due dates and completion evidence.
  • Resource allocation: Resource availability, assignments and scheduling conflicts.
  • Project management reports: Baseline-to-actual progress, effort and cost comparisons.
  • Purchase order management: Authorised supplier commitments and open line balances.

Configure, test and introduce the workflow.

  • Pick a current job. You hand over its stages and dates, and we build the timeline for you to read.
  • The project manager says what waits for what. A moving screen shows the effect of a changed date. You choose the dates the client may see. A client view arrives to try.
  • Supervisors learn to enter actual dates from the phone. A printed guide stays on site.

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.

  • A delayed prerequisite identifies its affected consultation stages without changing unrelated engagements.
  • Task completion requires the responsible person's update rather than the arrival of the planned date.
  • The schedule retains the previous commitment and the reason approved for a revised issue date.
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 project timelines with gantt charts?

Use when project stages depend on one another and delays affect later work. A project plan is created or its dates change.

What should we bring to the requirements discussion?

Bring anonymised examples of Consultation stages with their owner and planned completion dates.; Required plan and access prerequisites, client review points and the final issue milestone.; Consultant working calendars and the approved rule for changing commitments. 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. Show project tasks, dependencies and milestones on a calendar. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A timeline represents planned dates and dependencies. Task owners confirm progress, and resource owners confirm availability.

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. A delayed prerequisite identifies its affected consultation stages without changing unrelated engagements. Use this check when reviewing the first working version.

Talk to us

Discuss project timelines with gantt charts 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