User Guide

Sign in with the Microsoft account you already have - no new identity, no password to forget. The first person from your organisation to sign in is set as the admin, and your organisation is created automatically from your work-email domain.

The "Need admin approval" screen: dpow.app asks to read and write files in your own SharePoint, which most organisations require an administrator to approve once. If you see "Need admin approval", an administrator on your Microsoft tenant clicks "sign in with an admin account" on that screen, ticks "Consent on behalf of your organisation" and accepts - then every user in your organisation is cleared. This is a normal, one-time Microsoft step for any business app, and you only do it once.

Set your organisation and ISO codes in Settings - Organisation (name, originator and project codes, disciplines), so every output is named to the ISO 19650 convention automatically.

Define your CDE folder template in Settings - CDE Structure, then build the company scaffold in your SharePoint with one click.

To switch on the Outlook calendar, Microsoft To Do and report-by-email features, sign in with Microsoft once more so the connection carries the calendar and task permissions. Optional extras: bring your own AI key in Settings - Integrations, and link your mobile for WhatsApp status in Settings - Notifications - WhatsApp.

Sign in with the Microsoft account you already have - no new identity, no password to forget. Your organisation is recognised from your work email and provisioned automatically.

Add a client and a project. The project gets its ISO 19650 project code, and every register, view, report and invoice hangs off it from that moment.

Every project rides a status lifecycle - Enquiry, Proposal, Tendered, Won, In Delivery, Handover, Completed. It is always visible and it gates what you can do: the delivery register builds once the job is Won. Every transition is audit-logged.

dpow.app does not take your documents - it organises them where they already live. Adding a project builds the ISO 19650 CDE folder tree (WIP, Shared, Published, Archived, the working folders, and a Holding Area) in your own SharePoint tenant, with your permissions and retention policies.

Your organisation can define its own folder template in Settings - CDE Structure, then build the company scaffold with one click. Browse the live tree in-app at Documents (CDE).

Upload with the naming gate on: every file is checked against the ISO 19650 convention as it arrives. Conforming files file themselves; non-conforming ones are quarantined to the Holding Area for renaming, so the CDE never silently fills with junk.

When you stop using dpow.app your data does not get held to ransom: it is sitting in your tenant, in a folder structure that makes sense, because it always was.

The Generate button on the Dashboard runs the document skills: CAD fee proposal, scope of works / design brief, and project intake summary - straight from the tender files in your SharePoint plus anything you type. The output appears on screen first, then exports to .docx and .pdf.

Quick Fee Proposal turns a typed enquiry into a priced workbook (xlsx) that lands in the project CDE - the job starts before the job starts.

On Registers, the AI draft populates the deliverables spine from a pasted brief: 15-40 ISO-numbered rows, every one editable, never a locked output.

The Programme page plans dates onto undated deliverables inside your project window, with stage logic (architecture leads, structure follows, MEP after structure).

Export XLSX to CDE writes the live spine to your SharePoint WIP folder as an ISO-named TIDP / Master Data workbook.

One master record per deliverable - originator, volume, level, type, discipline, revision, CDE state, suitability, approval, RIBA stage, planned and actual dates and more - with controlled picklists keeping the data clean.

Views (TIDP, Programme, Dropline Gantt, Drawing Registry, MIDP) are live projections of the same spine, never copies that drift apart. Document numbers build themselves from the naming convention. Add a deliverable and it lands in every view, KPI and count instantly.

The ISO 19650 check validates state, suitability, revision and approval combinations and flags what fails - compliance you can see, in red, on the register.

Raise an RFI with its document reference, drawing link, cost and programme impact, required-by date and assignee. Click any row to work it: status changes, responses, snapshot attachments - everything audit-logged. Closing an RFI stamps the answered date automatically.

Draft with AI: describe the issue in a sentence and dpow.app writes the formal RFI, triages the discipline and priority, and cites the relevant standard plus your own spec section. You review and raise it.

Export an ISO 19650 -RI- register to the CDE. Open RFIs feed the dashboard KPIs and the weekly report narrative.

Technical Submittals: track product data, shop drawings, samples and mock-ups through the A/B/C/R review workflow, grouped by spec section, with snapshot attachments. Export an ISO -SH- schedule and a generated cover sheet per submittal to the CDE.

Risk schedule: a proper 5x5 likelihood-by-impact heat map, inherent versus residual scoring with RAG bands, the CDM living-document change history, and the chain back to the RFI or flag that raised each risk. The weekly report reads it directly.

Issue a transmittal and dpow.app records exactly which documents went to whom, at what revision and suitability, on what date - a frozen snapshot, immutable even as the live register moves on.

Export the transmittal sheet to the CDE. The golden-thread evidence that information was shared, never reconstructed after the fact.

The MIDP page is the Master Information Delivery Plan as a live roll-up of every task team’s TIDP, by discipline and by RIBA stage, with progress and CDE-state breakdowns.

Sync from CDE reconciles the register to the files actually in your SharePoint: it matches each file to its deliverable and flips the register state (WIP, Shared, Published) to match where the document really sits. The register tracks reality, not hope.

Raise a variation order with scope, cost and programme impact. It routes through OPEN, PENDING, CLOSED or REJECTED with evidence attached, and approval dates stamp themselves.

The phone-call variation that nobody wrote down stops existing as a category of risk.

dpow.app reads the register the way a programme director reads it: status codes, revision movements, comments, the live risk schedule, slippage - and writes the weekly narrative in board-ready English. Quantified, no waffle, ending with a directive for next week.

Reports are records: every report is a dated entity per project with its own lifecycle - Draft, Approved, Issued. The report canvas IS the report: drag the cards to reorder while it is a draft, edit or regenerate the narrative in place, then approve and issue.

Email it to the client straight from your own Outlook mailbox - they get it from you, not a noreply address. You stay the editor; it stops being the typist’s job.

Ask in plain English and get an answer in one box. About your data - "how many fire doors are Status C?", "what’s overdue on the MEP package?" - answered from your LIVE register, instantly, with exact numbers and the document references it used.

About the discipline - "what does Approved Document B require here?" - answered from construction knowledge, the standard explained and then applied to your project.

It remembers what you tell it per project, keeps your chat history, streams the answer as it thinks, and takes voice input free in the browser. A full-screen page and an always-on corner widget, on every screen.

Text the project for a live status from site. "1234 status" or "what’s overdue on Riverside?" sent to the dpow number comes back as a real answer from your live register - the same engine as dpow.chat, on the phone you already carry. It remembers the last project you asked about.

Security is built in: the phone number is the credential. The bot only answers a number linked to a verified dpow user, scoped to that user’s own organisation. An unknown number gets nothing; internal status stays internal. Link your number with a one-time code in Settings - Notifications - WhatsApp.

The right-hand panel is your live Microsoft 365, two-way. Calendar: your Outlook diary in-app, and one click pushes the project’s deliverable due-dates into it as events. To Do: a per-project task list - sync the open RFIs and overdue deliverables in, tick one off and it syncs straight back.

Lists: browse and edit your SharePoint Lists in the app. Meeting Minutes: capture the meeting and generate a versioned minutes document into the CDE. Time Tracker: log hours against the job, which feed the billing evidence. Spare Page: a private scratch note.

The same Microsoft connection that runs your CDE runs the cockpit - re-sign in with Microsoft once to grant calendar and task access.

A native task board for design teams - kanban with live status moves, plus the workload view showing who is over capacity before it becomes a missed deliverable.

Every move is audit-logged with what changed and who moved it.

Each client gets a branded, read-only portal at yourclient.dpow.co.uk, provisioned automatically when you add the client - no DNS tickets, no IT involvement.

They see the polished surface of the job: published documents, the issued report, the programme, and their stage invoices to pay - never your WIP, your workload or your internal notes.

The fee proposal becomes a stage-payment schedule - deposit, stage, final, editable. Issue each stage as a Stripe hosted invoice (no card data touches dpow.app); the client pays from a button on their portal; payment marks the stage paid automatically and the portal shows billed, paid, outstanding and next due.

The ledger exports as a QuickBooks-ready workbook into your SharePoint Finance folder. The tool that runs the design also collects the fee for it.

For Higher-Risk Buildings (18m or more, or 7+ storeys with two or more residential units), dpow.app builds your Building Safety Regulator Gateway 2 submission - the Building Control Approval application you make before work starts under the Building Safety Act 2022.

It is structured on the Construction Leadership Council (CLC) Gateway 2 guidance suite: the Application Information Schedule (GN04), Application Project Brief (GN05) and Folder Structure and Contents Schedule (GN06), plus the Application Strategy (GN07) and Staged Work statements (GN08) when staged.

Three outputs: a 109-task Gateway 2/3 tracker (nine phases, up to three tranches, a live progress dashboard) on Registers for any HRB project; the application pack generated from your project record and tender files, populated where the evidence exists and flagged [TBC] where it does not, exported to .docx; and an evidence-gap check that flags the holes that get a submission rejected - silent changes, superseded documents issued without a status, missing approvals, unnamed dutyholders - before the assessor finds them.

Every action lands in an immutable log that nothing and nobody can edit or delete. Compliance is not something you remember to do - it is a property of using the tool.

The Audit Trail page is the golden thread as a page: every event, filterable by entity and type, with the full detail payload one click away. When someone asks for the golden thread, you do not reconstruct it - you export it.

The AI features run on dpow.app’s engine by default, metered with a monthly budget so spend never surprises you.

An organisation that prefers its own provider can bring its own OpenAI or Anthropic key - or any OpenAI-compatible provider - in Settings - Integrations. Keys are stored encrypted at rest and the AI runs on your account instead. You are never locked to one vendor.

The founding cohort shapes these first: photos from site analysed and answered by the chat ("does this detail match the approved drawing?"); voice notes transcribed into the record; each client connecting their own WhatsApp number; deeper accounting integrations; and a team-board layer over Microsoft Planner.