Skip to main content
GullySystem
Professional services

Workflow and Approvals for Architecture firms

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 approvals around an identifiable design option or drawing revision and the authority allowed to decide it. Client selection, consultant coordination and the principal's technical review are different decisions. The next design stage should use the version actually signed off, while professional judgement and formal authority approvals remain with the qualified people and bodies responsible. Retain a client's approval of appearance or layout separately from the architect's professional review. The same drawing may require both, but one decision does not substitute for the other. Configuration should show which conditions remain before issue and identify the responsible reviewer instead of reducing the whole process to a single signed checkbox.

Bring the records the workflow depends on.

  • Design option or drawing revision submitted
  • Client and internal decision authority
  • Comments, conditions and required supporting documents
  • Stage-release and change-approval rules

Outputs to check

  • Version-specific design decision record
  • Outstanding comments and approval conditions
  • Approved-stage handover evidence

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.

Project architect

Submits the proposed design with the decision requested and resolves technical comments.

Client liaison

Collects the authorised client's response and distinguishes preferences from a confirmed instruction.

Principal or technical reviewer

Records the professional review and decides whether internal issue conditions are met.

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.

Two client representatives disagree

Refer the choice to the agreed decision-maker rather than treating either message as final approval.

Approval has conditions

Keep the unresolved conditions attached to the stage handover.

Design changes after sign-off

Submit the affected revision for the required decision and preserve the previous approval.

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 approval identifies the exact option or drawing revision reviewed.
  • Conditional acceptance does not appear as unconditional technical release.
  • A later change cannot inherit the earlier version's approval without the defined review.
Architecture firms

How the business operates.

Architecture Firm Management Software is a practice system that GullySystem sets up for architects, from single-architect studios to firms with project architects, draughtsmen and site supervision. It holds plot details, numbered drawing revisions, authority submissions, consultant lists and site visit reports, and each bill matches the fee agreed for its stage. Nothing is retyped between them.

Projects and site records

Hold the plot, site address, survey number, plot and built-up area, building type and the appointment terms for each project, so nothing about the brief is searched for. Site facts sit together.

Design stages and milestones

Move a project through concept, schematic, detailed design, good-for-construction and site stage, with the date each stage was reached and who moved it. Stages are visible across jobs.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Projects and site records. Hold the plot, site address, survey number, plot and built-up area, building type and the appointment terms for each project, so nothing about the brief is searched for. Site facts sit together.
  • Design stages and milestones. Move a project through concept, schematic, detailed design, good-for-construction and site stage, with the date each stage was reached and who moved it. Stages are visible across jobs.
  • Drawing register and revisions. Number every plan, section, elevation and detail, and keep each revision with its reason, author and date in one register, so the current sheet is never in doubt. Superseded sheets are marked.
  • Drawing issue and transmittals. Record which set went to the client, consultant or contractor, as a print, a PDF or a message attachment, and whether anyone acknowledged receipt. Holders of old prints show up.

Operational bottlenecks to check

Drawing revisions lose their trail

A plan goes out as one revision, then another, and the site builds from an older print, while the date and recipient of each issue sit in mail threads. Nobody can prove who held which print.

Design stages are not visible together

Concept, schematic, detailed design and good-for-construction run at once across several projects, so nobody can say in a single place which job is sitting at which stage. The diary tells half of it.

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. Enquiry and brief

    An owner or builder arrives with a plot and a requirement, and the site address, plot area, rooms wanted and appointment terms are recorded against a new project. The brief stays with the file.

  2. 2. Concept and schematic design

    The studio prepares site analysis, concept options and schematic plans, each drawing takes a number in the register, and the client’s comments are logged against the option shown. Every choice stays traceable.

  3. 3. Approval submission

    Submission drawings are prepared for the local authority and lodged with the forms your office uses, and each submission, query and reply is dated and kept with the project. Anyone can pick up the file.

  4. 4. Detailed drawings and tender

    Good-for-construction sets, services drawings, door and window schedules and a quantity list are built up, consultant inputs are logged as they arrive, and tender sets go out to contractors. Each tender set is numbered.

  5. 5. Construction stage

    Site visits are logged with photographs, deviations and instructions for the contractor, and revisions raised on site are numbered and reissued to everyone holding the older print. Old prints are withdrawn.

  6. 6. Stage billing and handover

    A completed stage is marked and a bill goes out for the amount set in the appointment, while as-built drawings and the final set are handed over and recorded. The file then closes.

Industry reports to connect with

  • Projects by design stage and project architect
  • Drawings issued and revisions pending by sheet number
  • Authority submissions and queries open
  • Site visits made and snags closed by contractor

Questions before implementation.

When should architecture firms 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 Design option or drawing revision submitted; Client and internal decision authority; Comments, conditions and required supporting documents; Stage-release and change-approval rules. 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 approval identifies the exact option or drawing revision reviewed. 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