Skip to main content
GullySystem
Professional services

Document Management for Architecture firms

Store business papers with their owners, versions and renewal dates.

Human Resources

Does this function belong in your operation?

Use when business documents are scattered across folders or inboxes.

A document arrives, changes or approaches expiry.

Configure the practice's filing structure so a plot record, fee agreement or consultant appointment is not confused with a drawing approved for issue. The library should identify author, date, document status and who can open it. Drawing transmittals and client sign-offs remain separate linked events; storing a file does not demonstrate that a contractor received or accepted it. Preserve the relationship between the project record and the practice's commercial file. Staff preparing a drawing need the applicable site information, while access to fee negotiations or appointment terms follows separate permissions. The search view should identify the document's purpose and status without exposing its contents to an unauthorised user.

Bring the records the workflow depends on.

  • Project and plot identifiers used by the studio
  • Document types including appointments, agreements and drawings
  • Author, revision, status and confidentiality rules
  • Required retention and renewal decisions

Outputs to check

  • Searchable project and practice-file register
  • Document version and access history
  • Missing agreement or superseded-file review list

Follow the document management workflow.

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

  1. 1. Register the document

    Assign its owner, type, business reference and relevant dates.

  2. 2. Check the file

    Confirm readability and whether it is a draft, signed copy or replacement.

  3. 3. Set access

    Apply the approved audience before wider sharing.

  4. 4. Issue a version

    Retain earlier copies and identify the version currently in use.

  5. 5. Review or retire

    Record renewal, replacement or authorised archival without losing required history.

Who uses the module, and who approves?

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

Studio administrator

Files signed appointments, consultant records and project papers under the correct reference.

Project architect

Identifies the working drawing version and records when a document is ready for the separate review or issue process.

Practice principal

Approves access to confidential commercial files and decisions on retention or external sharing.

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.

Fee agreement is unsigned

Keep it distinguishable from an executed appointment and assign follow-up.

Drawing filename lacks a revision

Require the author to identify its status before presenting it as the current sheet.

External consultant receives broad access

Limit sharing to the agreed project files rather than exposing unrelated commercial records.

Can this work independently?

This can operate as a controlled document library without accounting or HR modules. Links to contracts, suppliers or employees attach files to business records; reminders require the agreed notification channel and recipient rules.

Systems and records it connects with

  • Contract management: Operative agreement terms, amendments and obligation dates.
  • Vendor management: Approved supplier identities, terms and sensitive-change controls.
  • HR document management: Restricted employee documents and completeness status.
  • Notifications: Approved event messages and delivery or failure status.

Configure, test and introduce the workflow.

  • Start with an inventory. You tell us the kinds of papers and where they sit now, and we return folders by type and the dates that matter.
  • The owner says who may open which type. You get a role screen to check. Hand over a sample. A trial import of your scans and files comes back with fields filled and gaps marked.
  • Whoever scans and uploads practises naming, dates and linking. That group is trained before the rest.

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 user can identify whether an appointment is draft or executed.
  • A superseded drawing remains available without appearing as the current working version.
  • Access tests protect fee and contractual files from unauthorised project participants.
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 document management?

Use when business documents are scattered across folders or inboxes. A document arrives, changes or approaches expiry.

What should we bring to the requirements discussion?

Bring anonymised examples of Project and plot identifiers used by the studio; Document types including appointments, agreements and drawings; Author, revision, status and confidentiality rules; Required retention and renewal decisions. 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. Store business papers with their owners, versions and renewal dates. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Storage does not establish legal validity or provide legal review.

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 user can identify whether an appointment is draft or executed. Use this check when reviewing the first working version.

Talk to us

Discuss document management 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