On the first day of a job the package already knows every document each machine will owe, because that comes from the equipment type rather than from somebody remembering. It holds none of them yet, so it reads 0%.
Every photograph, reading, test and sign-off lands in it the moment it is captured. The percentage moves as the work happens, and at any point you can see exactly which documents are outstanding, on which machine, and who owes them.
There is nothing to assemble at the end, because there is nothing left over. A finished job is one where the list ran out.
A worked example: a data hall with sixty machines opens at 0% because nothing has been captured yet, and by week six it reads 41% — not because someone typed a bigger number, but because 41% of the individual document rows across every machine have actually been reviewed and approved. A UPS with its delivery inspection, anchor-torque reading, nameplate photo and installer signature all closed shows as ready; the chiller two rows down that is still owed a start-up report does not, and the package says exactly which report and whose desk it is on.
Not every required document survives the job unchanged. A requirement can be waived — a submittal the owner agreed wasn't needed for this particular unit — and a waiver is recorded the same way an approval is: who decided it, and why. That call belongs to the project manager or the firm's manager, not to whoever is closest to the line; a technician records evidence and cannot waive the requirement to produce it. Nothing quietly drops out of the count instead of being accounted for; a document is either closed, waived with a reason on record, or still owed. A waiver can be withdrawn later, and both decisions stay on the record.