Where the samples come from

The 265 rows are the Solene finishes schedule as extracted, numbered #1 to #265. The number is the permanent identity of a row: codes repeat and a few rows have none, so QR labels and links use the number. Samples can also be added by hand.

Deciding whether a sample is needed

Every row starts at TBC. The Development signer, or an administrator, sets Sample required to Yes or No. No moves the row to Not Required and it leaves everyone’s queue. Yes moves it to Pending Review and it appears in the signers’ Awaiting me lists.

Consultants sign first

Where a sample needs a consultant’s technical sign-off, an Editor attaches that consultant to the row. The panel (Development, Architect, Builder) cannot sign until every attached consultant has, in either order among themselves. Attaching a consultant to a sample that already carries signatures starts a new revision, because those signatures were made without the consultant’s check; removing one never does.

Tech data and physical samples

Tech data and Phys sample are each Yes, No or N/A; a blank means nobody has assessed it yet, which is different from not applicable. Files go on the Form: drop a tech data sheet or a photo onto the zone. Photos are downscaled in the browser before upload. Nothing is ever overwritten; a newer file supersedes, and every earlier version stays openable, because a signature was made against a particular version.

Rejection and resubmission

A rejection sets Rejected. Request resubmission on the Form starts a new revision: the earlier decisions stay in the record and stop counting, and the row returns to Pending Review. When the new sample has physically arrived, Mark as resubmitted records that in the audit trail. A rejection on a second or later revision shows as Resubmit Required: same state, one more time round.

QR labels

Tick rows on the Register and click QR labels. Labels lay out on Avery L7126 sheets and each code opens that sample’s record for anyone signed in. Print and Mark as printed are separate, because the browser cannot know whether the printer ran. Marking records the revision printed; the Changed since last print count is every row whose revision has moved since, and it reads 265 until the first labels are marked.

Samples Meeting

An administrator hosts it from the Register, ticks who is in the room and walks through the samples awaiting the host’s own signature. Attendance goes in the minutes. Other people’s slots still need their own login.

What the statuses mean

Status is worked out by the database from Sample required, the attached consultants and the signatures on the current revision. Nobody sets it by hand.

How signing works, on both registers

Every approval slot is held by one named person. Only that person can sign it, from their own login, whoever is holding the device. There is no delegation yet: if the named signer is away, the slot waits.

Signing opens a short ceremony: read the attestation, tick that you adopt the typed name as your signature, type your name, then choose Approve, Approve with comments or Reject. The last two require a comment, and the comment is part of the signed record. The Sign button stays grey until the name is typed and the box is ticked.

The database, not the browser, stamps the time and seals each signature into a hash chain for the project. Signatures are never edited or deleted. A new revision starts the approvals again; earlier signatures stay in the record at their own revision and simply stop counting.

Verify seal, on the Audit tab, re-walks that chain and reports every signature it checked. It proves nothing has changed since signing. It does not, on its own, prove a signature to an outside party, and during the pilot the existing email and spreadsheet process remains the contractual record.

Notifications are a prompt, not the record

Emails come from REVEAL DM <noreply@notifications.revealdm.com> and replies reach a person. If an email is late or missing, nothing is lost: the register itself is authoritative, and the Awaiting me filter on the Form tab is the reliable list of what needs your signature.

Changes made by colleagues appear on your screen as they happen. If something looks stale, reload the page.