Packages — the register

Open this screen in Saral/projects/subcontractors/packages

One row per work package, let or not: code, title, element, type, who runs it, how far design and construction have got, and the four columns the client's schedule prints. Every other Subcontractors page works over this list, so it is the first thing to set up — the first tab of Appointment.

You enter

The package register — code, title, trade — or bring it in from the Payment Schedule / a won tender
A dated update per discipline, never one comment cell overwritten

Saral fills in

Each package's status (planned → tendering → appointed → on site → complete) from the record
Design % from the drawings register, construction % from the application's CSA lines, and the Schedule columns
What the firm still owes for the month, each item missing, received or expired, with where Saral knows it from

It produces

The Schedule of Sub-Contractors for the client (PDF, Excel, email)
The “what you owe us” email, sent from your own Outlook

Packages: status comes from the record

You never tick a package forward. Issuing a tender makes it tendering, Appoint makes it appointed, the first head count or application makes it on site, and the PC certificate makes it complete. Design % is read from the drawings issued to the package and construction % from the application's contract sum analysis lines; type a figure only where the register is incomplete, and say why. What each discipline says about a package is a dated history, never one comment cell the next person overwrites. A package here and a package on the Payment Schedule are the same thing seen twice — the import suggests exact matches and a person accepts each link.

Next screen: /projects/subcontractors/procurement

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.