Project assumption interview notebook

For project initiation facilitators, turn consented workshop notes and project briefs into stakeholder-reviewed assumption brief. Address this specific problem: stakeholders disagree on unstated assumptions. The aim: surface disagreements before planning hardens. The pilot tests whether that benefit holds up against reviewer effort and real operating costs.

The buyer creates a project, supplies consented workshop notes and project briefs, and confirms scope and access. Users correct extracted facts, resolve flagged uncertainties and approve the final stakeholder-reviewed assumption brief before use. Retain source links and a version history for the next cycle.

How the AI works

AI assists these bounded tasks: extract implied assumptions; compare stakeholder statements; draft clarification questions. Use only consented workshop notes and project briefs and preserve uncertainty in stakeholder-reviewed assumption brief. Keep model suggestions separate from verified facts. Link factual outputs to authorized input evidence and show missing information explicitly. Use deterministic checks for counts, dates, identifiers and arithmetic where applicable. A designated reviewer validates consequential outputs and signs off the delivered result.

Safeguards

Confirm owners, decisions and commitments. Keep employee discussion notes access-controlled and avoid covert individual performance inference. One organization, one defined input format and one representative pilot batch using consented workshop notes and project briefs. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Require appropriate access and publication approval. Preserve source material, label AI drafts and make corrections traceable. Measure false positives and missed cases alongside speed.

What to build first

Costed pilot: One organization, one defined input format and one representative pilot batch using consented workshop notes and project briefs. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: extract implied assumptions; compare stakeholder statements. Support the third task through an assisted review queue: draft clarification questions. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of stakeholder-reviewed assumption brief. Authentication, account isolation, deletion controls and basic operational logging are included. Specialized production certification, live write integrations and broader rollout are not included unless explicitly stated.

What it can connect to

Team updates, calendars, project records and agreed management routines. Case management, customer records, document storage and notification systems. Begin with an exportable review pack before automating destination writes. Begin with uploads and exports of consented workshop notes and project briefs. Any named system or connector is a candidate requiring current access and compatibility checks; no live connection is included by default.

The screens in detail

Give submitters a mobile-friendly step-by-step form with document uploads and a visible completeness checklist. Staff see a queue with missing items and extracted fields. Place the original document beside each uncertain value. Show submitted, clarification required and ready-for-review states. Open with brief and sources; move into project assumption interview notebook for the detailed task; finish in review and delivery for review and handoff. Show the source record, uncertainty and approval status beside each proposed output.