Skip to main content
GullySystem
Project Management · Solutions

Keep each project’s drawings, approvals and photographs in one place, by version.

Project document management keeps drawings, approvals, contracts and site photographs in one place per project, with a version number on each. The newest drawing is obvious, and the old one is still there when somebody needs to prove what was approved. Who may open which folder is decided by you, and not by whoever forwarded it last.

What it is

Drawings travel by WhatsApp, and WhatsApp compresses them. There is a Rev C in the architect’s mail, a Rev D somebody sent to the site group, and a print on the wall of the flat that nobody can date. The carpenter uses the print on the wall.

Each project gets one place for its documents. A new version does not overwrite the old one. It sits above it, stamped with the upload date and the uploader’s name. The site opens the project on a phone and gets the current drawing, and not the one that was forwarded fastest.

What it replaces

What your team uses today.

The module takes over these, one at a time, so nothing has to stop while it is set up.

  • A chat group full of drawing attachments
  • An email folder per project
  • A pen drive carried to site
Where it goes wrong today

The problems this is meant to ease.

The latest drawing is unclear

Several copies of a plan circulate in chats. The site follows an old revision and the error shows up in concrete.

Approvals live in messages

A client says yes in a voice note. Months later, nobody can show who approved what.

Access is whoever forwarded it

A vendor receives commercial papers meant for the office. Sharing is decided by habit.

Photographs lose their context

Site pictures sit in phones with no date or stage attached. Arguments about progress are settled by memory.

Search means scrolling

A drawing from March is somewhere in a long chat. Finding it takes longer than redrawing it.

Inside the module

What project document management does.

One home per project

Drawings, the contract, approvals, bills of quantity and site photographs, under folders named the way your office already names them.

Versions, not replacements

Rev C stays when Rev D arrives. The current one is marked, and the old ones can still be opened.

Approved, and by whom

A drawing sent for approval comes back approved or with comments, and the date sits on the file for ever.

Who may open what

The client sees what you share. A vendor sees only their own scope. Commercial documents stay with the office.

Site photographs by date

Progress photographs from the phone, filed against the project and the stage, which settles most arguments about what was done when.

Found by searching

Search by project, drawing number or date and do not scroll a chat from March.

Where it gets used

What this looks like in a working week.

Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.

A new revision arrives

The architect uploads Rev D. It is marked current, Rev C stays available, and the site engineer is told.

A drawing goes for approval

The client reviews and comments. The approval date and the person sit on the file.

A vendor needs their scope

The project manager gives a vendor access to a folder. Commercial documents stay with the office.

A dispute about progress

The supervisor opens site photographs by date and stage. The disagreement is settled from the record.

Who touches it

The people who open this every day.

Site supervisor

Opens the latest drawing on a phone and uploads today’s photographs before leaving site.

Architect or designer

Issues a revision and knows it has replaced the earlier one everywhere it matters.

Project manager

Sends drawings for approval and chases the ones the client has been sitting on.

Owner

Has the contract and the approvals in one place when a dispute arrives eighteen months later.

How it is set up

From first conversation to daily use.

  1. Look at your folders

    You show how projects are filed today. You get a proposed folder layout that follows your office naming.

  2. Import a live project

    Documents from a running project are loaded with their revisions. You check that the current ones are marked correctly. Revisions are the usual trap.

  3. Set access rules

    You decide what clients, vendors and staff see. Each group gets a test login.

  4. Add the phone routine

    Site staff upload photographs and drawings from their phones. The routine is shown on site.

  5. Move the remaining projects

    Further projects are brought across in turn. The old chat folders are marked as closed.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Documents with a current version marked
  • Drawings sent for approval and not yet returned
  • Folders opened by people outside the office
  • Site photographs filed against a stage
  • Searches that end in a document opened
How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Task management
  • Project timelines with Gantt charts
  • Client portal
  • Contract management
  • WhatsApp
Common questions

Questions owners ask about project document management.

Is Google Drive not enough?

For a small studio it often is, and you should not pay for more. Drive gives up when a drawing needs a formal approval, when vendors must see one folder only, or when nobody can say which revision went to site.

Will drawings open properly on a phone?

PDFs do, and that is what site people open. Heavy CAD files download to a laptop instead, which is where they were going to be opened anyway.

Can we stop a vendor seeing our rates?

Yes. Access is set per folder and per person, so a fabricator sees their own drawings and nothing about what the client is paying.

Where do the files actually live?

On cloud storage we set up for you, backed up, with the account in your name. If you leave us, the files stay yours. Our interior design system keeps a design library and client approvals against each project in the same way.

What drives the price of project document management?

The count of projects, users and the volume of files drive it. Client portal access and links to tasks add effort. The price of project Document Management follows what you include, and the quotation shows each inclusion separately. Scope sets the figure.

How long does it take to get projects filed?

How tidy your present folders are decides it. A release with a project’s folders, versions and access can come early. You supply the documents and the access rules, and the proposal lists dates.

Talk to us

Tell us how you handle project document management today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements