Service

Struggling to keep track of approvals?

An approval workflow inside your own Microsoft 365 that leaves a traceable, auditable record against the version it approved. No new platform, no subscription, yours to keep.

The deliverables are in one place. The approvals are in six.

Your project deliverables are in SharePoint. The approvals are in an email, a Teams message, a phone call, a conversation by somebody’s desk, or written on the deliverable itself.

They are all real approvals. None of them is a record. Nobody can say for certain whether a document has been approved, someone loses an afternoon finding the evidence when a client or an auditor asks, and when it turns up you often cannot tell which version it was approving.

What the workflow does

Stops unchecked work reaching a reviewer. You decide what the author must self-check. The workflow makes them confirm each one before they can submit, so reviewers stop spending their time finding basic errors.

Routes it to the right person. Named approver, notified in Teams, with the document and what they are approving in front of them.

Records the decision as it happens. Who approved, which version, and when.

Files the result. A PDF of the approval record, into the project’s Approvals folder, beside the document it approves.

Without buying a platform

Firms usually solve this by procuring Procore, Autodesk Construction Cloud or Aconex. Capable products that earn their cost for a large contractor. For a firm of twenty, the price is one problem and moving your deliverables into a second system is another.

This runs in your own tenancy. Nothing procured, nothing migrated, and no data leaves your Microsoft environment.

What you receive

  1. One approval workflow, live on a real project in your own tenancy
  2. Self-check requirements built into the submission, set by you
  3. The approval request form and routing rules, set up with you
  4. Automatic filing of the approval record against the version approved
  5. Documentation written for whoever has to change it later
  6. A working session with the people who will use it
  7. Ninety days of support after go live

One workflow means one approval type. A second is quoted separately.

Price

NZ$4,000 + GST. No subscription and no per user charge. It keeps running whether or not you ever speak to us again.

What you end up with

  • A record of who approved a document, which version, and when
  • Unchecked work stopped before it reaches a reviewer
  • The approval record filed automatically, beside the document it approves
  • No new platform procured and no deliverables migrated

Where to start

Approval workflow build

One workflow means one approval type. A second is quoted separately. NZ$4,000 + GST. No subscription and no per user charge. It keeps running whether or not you ever speak to us again.

Common questions

How is this different from Procore or Aconex?

Those are platforms with their own repository, so adopting one means moving your deliverables into it. This adds the approval and the record to the SharePoint you already use. It does far less, which is the point at this price.

Where does our data go?

Nowhere. It stays in your Microsoft tenancy, under the access controls you already have.

Does this cover Producer Statements?

No. Producer Statement authorship and the review planning behind it sit in the Technical Review Framework. This approves the deliverable and keeps the record.