All work

BRICK PMS / Corporate workflows & document management

Document and workflow management for project teams.

BRICK PMS enables project partners and internal teams to manage forms, documents and approvals in a shared workspace. Tailored forms, attachments, review notes and decisions are linked to the same record. Completed records remain accessible in the archive with their documents and activity history.

In active use · Ongoing development
  • Forms that fit the work
  • Workflows across teams
  • Corporate archive
Product owner
ERYA
My role
Lead Software Developer

Tracking a document through its workflow

Responsibility and status information is retained through preparation, review, completion and archiving. User permissions determine access.

BRICK PMS
Sample campus Illustrative workspace

Shared record / SAMPLE / DRW / 001

Drawing review

Prepared

Document review form

Architecture / Revision 02
Project
Sample campus
Discipline
Architecture
Document
Ground-floor plan
1Contractor

Document information

2Consultant

Review & notes

3Client

Decision

Attached files02

PDFsample-plan.pdf
PDFreview-notes.pdf
Project documents · Company processes · Shared archive

Workflow 01Choose a form suited to the process, complete the relevant fields and attach the supporting files.

Illustrative product view with sample data.

01 / BRICK PMS

From form design to approval and archiving

A project document may need contributions from several companies. An internal request may move between an employee, coordination, management and administration. BRICK PMS brings these contributions together through forms shaped around the work, keeping responsibilities, decisions, attachments and changes connected.

02 / BRICK PMS

Collaboration and record integrity

01

Collaboration across companies

Client, consultant and contractor teams contribute to the same document. As it moves between participants, each contribution and action can be followed in the shared record.

02

Forms shaped around the process

Fields and layouts fit the work. Different roles have their own sections within the same form, while supporting files stay with the record or a specific entry.

03

Task, responsibility and status tracking

Task and project views bring active, followed and completed work together. Teams can see who holds a task, what is pending and which deadlines need attention.

04

Decisions with their context

Review notes, requested changes, decisions and revisions stay with the document. Later attachments are part of its history, alongside the explanations that led to the outcome.

05

Access that reflects responsibility

Access can be defined by project, team, role and document. Participants from different companies share the workspace within the scope of their permissions.

06

Archives with documents and activity history

Completed project documents and internal records remain together with their files and activity history. Teams can revisit, download or print the information they are entitled to access.

03 / BRICK PMS

Project and internal use cases

ArchitectureRevision 02
review-notes.pdfSAMPLE / DRW / 001
Concluded

Entrance layout updated. Previous comments are retained in the document history.

Technical drawing review

A drawing moves between the relevant teams. Review notes, requested corrections and added files are followed in the same record. The revision explanation and earlier actions remain available with the final decision.

Advance & expense request

  1. 01

    Employee

    Request & supporting files
  2. 02

    Management

    Review & approval
  3. 03

    Administration

    Payment & closure record
Attached files

Managing an advance and expense request

Employee details, coordination and management approvals, and administrative payment and closure records have their own sections in one form. Expense entries stay connected to their supporting documents. Leave requests, assignments and equipment handovers are other examples of internal use.

Illustrative product view with sample data.

04 / BRICK PMS

My development scope

My development work at ERYA covers form design, document-based workflows, tasks and approvals, and permission-based archive access. I work on the structure that keeps forms, attachments and activity history connected.

BRICK PMS is a web application built with PHP and MySQL, with jQuery and Bootstrap for the interface. My work connects configurable forms, attachments, permissions and revision history within the same document workflow.

The BRICK PMS brand and product rights belong to ERYA. This page presents my software development work on the project.

Contact

Projects and collaboration

I work remotely from Bodrum on software and product development. If you're building a web or mobile product, business application or AI-assisted workflow, contact me on LinkedIn with some context about the project and what you need help bringing to production.

Contact me on LinkedIn