Skip to main content
GullySystem
Professional services

Project Document Management for Architecture firms

Keep project documents tied to the correct job, revision and approval.

Project Management

Does this function belong in your operation?

Use when project work depends on drawings, specifications, approvals or shared files.

A project file is issued, revised or approved.

Treat a drawing issue as a controlled event, not merely a file upload. Configure each transmittal with the sheet references, revisions, purpose of issue and recipients, then retain acknowledgement separately. A contractor may hold a construction issue while the client reviews a later option, so the register must show which version each party was authorised to use. A transmittal should retain the issue purpose used at that moment, such as review or construction, rather than display only today's file status. That distinction matters when reconstructing which instructions a site team had. The authorisation to issue and the acknowledgement of receipt should be visible as separate events in the register.

Bring the records the workflow depends on.

  • Project drawing register and revision identifiers
  • Issue purpose and approved sheet set
  • Client, consultant and contractor recipient lists
  • Review decisions, transmittals and acknowledgements

Outputs to check

  • Drawing transmittal and recipient register
  • Current authorised issue by recipient
  • Outstanding review and superseded-sheet action list

Follow the project 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 submission

    Identify project, document type, revision and author.

  2. 2. Check completeness

    Confirm the file and supporting references are ready for review.

  3. 3. Collect approval

    Record reviewer comments and the authorised decision.

  4. 4. Issue the version

    Make the approved copy identifiable to its permitted audience.

  5. 5. Control replacement

    Retain superseded files and notify affected work owners of the change.

Who uses the module, and who approves?

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

Document controller

Assembles the approved set and records exactly what was issued to each party.

Project architect

Confirms issue status and resolves conflicting comments before another revision is released.

Consultant coordinator

Tracks missing responses and checks whether specialist drawings align with the architectural issue.

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.

Only part of a set is revised

Identify changed sheets and preserve unchanged revision references in the transmittal.

Contractor uses a superseded detail

Record the discrepancy and obtain the architect's instruction rather than silently replacing the evidence.

Recipient does not acknowledge

Keep receipt status unresolved and assign the required follow-up.

Can this work independently?

A project document library can operate independently with project identifiers and access roles. Tasks and timelines link to approved files, while a client portal controls external sharing. Uploading a drawing does not approve it for construction, manufacture or another regulated use.

Systems and records it connects with

  • Task management: Assigned work, due dates and completion evidence.
  • Project timelines with Gantt charts: Planned dates, dependencies and recorded milestone progress.
  • Client portal: Permitted customer documents, requests and account views.
  • Contract management: Operative agreement terms, amendments and obligation dates.

Configure, test and introduce the workflow.

  • You show how projects are filed today. You get a proposed folder layout that follows your office naming.
  • Documents from a running project are loaded with their revisions. You check that the current ones are marked correctly. Revisions are the usual trap. You decide what clients, vendors and staff see. Each group gets a test login.
  • Site staff upload photographs and drawings from their phones. The routine is shown on site. Further projects are brought across in turn. The old chat folders are marked as closed.

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 past transmittal can reproduce its exact sheet and revision list.
  • The recipient register distinguishes review copies from authorised construction issues.
  • Later revisions do not overwrite the record of what a contractor previously received.
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 project document management?

Use when project work depends on drawings, specifications, approvals or shared files. A project file is issued, revised or approved.

What should we bring to the requirements discussion?

Bring anonymised examples of Project drawing register and revision identifiers; Issue purpose and approved sheet set; Client, consultant and contractor recipient lists; Review decisions, transmittals and acknowledgements. 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. Keep project documents tied to the correct job, revision and approval. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Engineering approval and contractual interpretation remain with the authorised professionals.

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 past transmittal can reproduce its exact sheet and revision list. Use this check when reviewing the first working version.

Talk to us

Discuss project 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