| Discipline | Company (on Solene) | Other PACE Projects | Primary Contact |
|---|
| Order | Role | Entity | Approver | Channel | Tier |
|---|
Who holds each slot, and which slots exist. A slot that has been signed cannot be removed. Delegate lets a colleague from the same company sign while the approver is away; a single DCR can also be handed on from its form.
Consultant and Subcontractor memberships work the same way, plus any approval slot they are named on.
Click + New DCR on the Register. The number is allocated by the database the moment you click, so numbers are never reused; a gap in the sequence means a DCR was started and abandoned, and that is normal. Fill in the title, the description of the change and the original design, pick Raised by and the Discipline affected, then set the Cost impact.
A DCR with a cost impact sits at Pending Cost Review until a Priced value is entered. Once priced, the database decides who has to sign: at or below the escalation threshold in Settings, the three standing approvers; above it, the Escalation slot is required as well and the status reads Approval Required. Change the threshold and every DCR re-routes; nothing needs re-entering.
A drawing must be attached. The Form shows what is blocking sign-off rather than hiding the buttons. Approvers sign in any order; the register is set to parallel approval, and only a project administrator can change that.
A rejection sets the status to Rejected and notifies whoever raised it. To go again, open the Form and start a revision: the revision number goes up, the earlier signatures stay in the record, and the DCR returns to the workflow from its current cost impact. Reopening a withdrawn DCR also starts a new revision, so reviewers can tell that parked information was re-checked.
The DCR is Approved, or Approved with comments if any signer added conditions. Print the notice from the Form: it carries the approval record, who printed it and when, and a statement that it is a copy of a register record rather than a contractual document.
An administrator hosts a meeting from the Register, ticks who is in the room, and walks through the DCRs awaiting the host’s own signature. Attendance is recorded in the minutes. Other people’s slots still need their own login; the meeting shows what is still outstanding and who it waits on.
Status is worked out by the database from the priced value and the signatures on the current revision. Nobody sets it by hand.
| Status | Meaning |
|---|---|
| TBC | Cost impact not yet chosen |
| Pending Cost Review | Has a cost impact, not yet priced |
| Pending Review | Priced at or below the threshold; waiting on the standing approvers |
| Approval Required | Priced above the threshold; the Escalation slot must sign too |
| Approved / Approved w/ Comments | Every required slot has signed on the current revision |
| Rejected | A signer rejected the current revision; start a revision to continue |
| Withdrawn | Taken out of the workflow; can be reopened as a new revision |
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.
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.