Construction management software for Malaysian contractors

The project holds the client, site, contract sum, dates, and status. A variation holds a description, the QS’s value, status, and a link to the instruction. A progress claim holds the period, the amount applied, the pack, and later the certified and received amounts if you record them. A subcontractor bill holds the package, the amount, and whether it was accepted. Each of these has a person and a time when status changes.

Site evidence is an attachment on the project or on the variation: a photo, a signed instruction, a delivery note. Supervisors need a short path to add it. The QS needs to find it while preparing the claim. If adding a photo takes a training course, it will stay on the phone.

Reports in version one are short. Open projects, variations awaiting approval, claims not yet certified, bills accepted but not marked paid. A director can live on that list. A fifty-widget dashboard before the statuses mean anything is decoration. We will push the short list first.

A variation starts because something changed: a client instruction, a site condition, a design clarification. The record names that cause and holds the backup. The QS enters the value when the value exists. A director approves above the limit you set. Below the limit, the project manager’s role may be enough. The approve button is absent when the user is outside the limit.

Status words should be few: draft, submitted internal, approved, rejected, included in claim. Teams that invent ten synonyms for “maybe” cannot report. We will suggest a short list. Your commercial lead has to accept it. Once approved, the value rolls into the current contract picture as a stored total, not as a formula nobody signed.

Rejected and withdrawn variations remain visible. Deleting them is how a later dispute loses the fact that the item was considered. If the client later accepts a rejected item, that is a new approval, not a quiet edit of the old row.

Preparing a claim can still happen in the QS’s workbook if that is where the measurement lives. The system’s job is the pack that was actually sent: the period, the summary numbers, the PDF or export, and the moment it was marked submitted. A second submission in the same period is a revision with its own file, not an overwrite.

Certification is a different event from application. When the client’s representative certifies a lower figure, the file stores both. Receipt of money is a third event, entered by accounts when the bank shows it. Applied, certified, and received are allowed to differ. Hiding the gap is how cash flow meetings become arguments about which sheet is newer.

Backup documents—measurement sheets, photos, signed daywork—attach to that claim. The QS should not keep the only full pack in a personal laptop folder named FINAL2. If a laptop disappears, the project file is the pack. That is the practical reason to buy the system.

Each subcontractor package sits under the project. Bills arrive, get checked, and are accepted or queried. A query is a status with a note, not a lost email. Back-charges against the subcontractor need a reason and an amount your commercial team entered. The net figure approved to pay is what accounts should see.

The system does not pay the subcontractor. It records the approval. Payment runs through the bank and the ledger you already use. An export can come later so accounts is not retyping the approved total. Doing the export before the approval status is trusted will export the wrong number efficiently.

Retention on subcontractor bills can be a field you enter, with a release date. The same rule as client retention applies: the date can remind you. It cannot decide that defects are closed. Name the person who marks the release approved.

A supervisor sees the jobs they are on, can add a photo or an instruction, and can raise a material request. They do not edit contract sums. A project manager sees dates, open instructions, and requests. A QS sees claims and variations. A director sees approvals above the limit and the short report. Accounts sees accepted bills and received amounts.

Shared logins break the trail. If the site uses one phone login for three supervisors, you will not know who uploaded the photo, and that is often acceptable for a photo and unacceptable for an approval. Approvals use named users. Photos can be slightly looser if you accept that limit and write it down.

Clients do not get a login in the first release unless you have a reason and a person who will answer what they see. A portal that shows a half-prepared claim creates disputes. Publish a pack when it is submitted, in a later phase, if you still want that.

Large project suites assume programmes, cost codes, and a team that will maintain them every week. They suit contractors who have already hired for that discipline. A commercial file for claims and variations is a smaller product. Sorable builds the smaller one. We do not implement those suites, and we do not resell them.

Workbooks remain right when one QS runs a single job and can still find last quarter’s pack. They fail when two project managers edit copies, or when a director cannot tell which PDF the client received. The audit looks for that copy problem. If we find one owner and one job, we will say a tighter folder is enough.

Drawing tools stay drawing tools. A link or an uploaded PDF of the current drawing is a reference on the project. Version control of CAD files is a specialist problem. We will not pretend a file upload is a drawing-management platform.

We will not produce quantities from drawings, price a bill of quantities from a rate library we invented, or certify work. We will not lodge CIDB or safety submissions. We will not give contract advice. The figures in the system are figures your people entered and are willing to stand behind.

We will not offer a way to replace a submitted pack silently. We will not scrape client mailboxes. Documents arrive because someone uploaded the instruction or the claim PDF. Personal data on those documents—identity cards of workers, if you choose to store them—should be limited to the role that needs them. Many contractors should keep worker identity in their existing HR process instead of copying it into the project tool.

We will not run the site. Chase of late claims is a queue the commercial lead owns. Software can show age. It cannot make the client pay.

Bring a redacted claim, a variation, and a subcontractor bill from the same job, plus the approval limits you wish you enforced. We map who retypes a number. That is the workflow audit. It can end with “do not build.”

The quote names one project type. Projects, variations, claims, and subcontractor bills for that scope often fall between RM20,000 and RM55,000 setup, plus monthly care. A client portal, a cost-code export to the ledger, and a second project type are additional. Timeline is often 8–16 weeks after approval.

The construction industry page explains the category choice. Document-management and ERP pages apply when the pain is the archive or the ledger rather than the claim. Sequence them. A claim that still lives in chat will not be fixed by an invoice module alone.