Build n BloomFit Call
Fit Note
- What we saw
- What you told us
- What we think might be true
- What we do not know
- One useful next step
Written byBuild n Bloom
To keep whether or not you proceed.
Saved outputs
Reviewed operational diagnostic
Harbour
- Contents
- Reviewed operational diagnostic
- Version
- Report 7 · source 1
- File
- DOCX
HarbourReport 7 · source 1
- The effort input is an estimate.
- Validate the period, job mix and available options before any commitment.
- This comparison does not establish staffing viability or guaranteed delivery.
HarbourDOCX
AI preparation; human wording and exact-version review
Reviewed operational diagnostic
Report 7 · source 1
For 26 October 2026, 300 available hours at an estimated five hours per job model 60 jobs; this is not measured throughput. The confirmed-only comparison uses 60 jobs. The planning register still contains 80 jobs, including 20 provisional jobs dependent on client access. If none of those provisional jobs release during the week, the confirmed-only comparison remains 60; if all release, the potential workload is 80 against the same 60-job model. The planning register remains 80 in both scenarios. These conditional comparisons do not establish delivery readiness, spare capacity, staffing need or a commitment. Confirm actual access-release dates, validate job mix and measured effort, and compare scheduling and service scope before deciding.
A delivery plan with role constraints
Birchwell
- Contents
- A delivery plan with role constraints
- Version
- Plan 3 · scope 4
- File
- TXT
BirchwellDOCX
AI preparation; human scope, estimates and internal decision
An internal proposal that carries its scope
Internal proposal 2
Which first onboarding process test should Birchwell choose after a checklist desk review and one internal workshop?
BirchwellInternal proposal 2
- A short internal options briefing: current-process observations from the supplied materials; comparison of (1) retaining/tightening the existing meeting and project-folder process and (2) adding a form; discovery hypotheses; first-test decision criteria; and explicit exclusions and unresolved acceptance conditions.
- No interviews, interview access, external contact, handover-file access, implementation or dashboard build.
- No claims of credentials, insurance, conflict clearance, resource availability, client agreement, budget, agreed fee, delivery date or award.
- Human estimates below are internal planning only.
BirchwellTXT
Human-entered assumptions; deterministic comparison
A delivery plan with role constraints
Plan 3 · scope 4
Analyst: available 24h; baseline 8h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Reviewer: available 6h; baseline 2h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Case-equivalent capacity 3 → 1.5; these are not scheduled/completed engagements.
An interpretation the reviewer can challenge
Northline
- Contents
- An interpretation the reviewer can challenge
- Version
- Report 12 · source 2
- File
- DOCX
NorthlineTXT
Actual AI response; Maya’s clarity edits; internal review
A response that addresses the actual concern
Working copy 26a56d09
You asked why the sponsor passage was called counter-evidence and whether three authored accounts supported a recurrence claim. The earlier counter-evidence label was an evidence-classification error. The sponsor’s account describes uncertainty about the decision awaiting action and the next owner; it supports investigating that uncertainty. It does not demonstrate that approval delays caused repeated questions, nor does it oppose the theme.
NorthlineReport 12 · source 2
- Evidence; 02-client-sponsor.txt: I could not tell which version the team was using.
- Reason and limits: Fresh method2 run still uses the same lead quotation as both support and counter-evidence.
- Human review distinguishes the claim being challenged from the theme itself.
- This is a new run-specific judgement, not an automatic carry-over of the earlier T1 correction.
- Three authored accounts establish no frequency, cause or demand.
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
Northline
9 saved outputs
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI response; Maya’s clarity edits; internal review
A response that addresses the actual concern
Working copy 26a56d09
You asked why the sponsor passage was called counter-evidence and whether three authored accounts supported a recurrence claim. The earlier counter-evidence label was an evidence-classification error. The sponsor’s account describes uncertainty about the decision awaiting action and the next owner; it supports investigating that uncertainty. It does not demonstrate that approval delays caused repeated questions, nor does it oppose the theme.
NorthlineTXT
Actual AI finance draft; human internal review
A reconciliation query, with the uncertainty intact
Working copy 7aa6ab2f
The supplied assertions reconcile deterministically to one invoice assertion, INV-NORTH-01, for AUD 100. They also contain a AUD 20 received-payment assertion, PAY-NORTH-01, followed by an exact AUD 20 reversal for that same payment. The payment’s net asserted effect is therefore AUD 0. The supplied reconciliation consequently reports matched receipt assertions of 0 and an asserted balance of AUD 100, labelled “No matching receipt.” No unmatched assertions or held reversals are supplied.
NorthlineTXT
Actual AI checklist; human internal review
A handover with named responsibilities
Working copy 4f081531
Nadia, the accountable sample lead, owns receipt and internal review of the remaining handover. Elena, in the departing sample role, owns preparation: identify remaining clarification support, record the retention obligation, and identify permitted Northline-only material. Rowan is the named sample receiver. The stated 29 October 2026 date is an internal target, not a client promise.
NorthlineTXT
Actual AI draft; Maya’s clarification; NOT REVIEWED
A draft that cannot clear an unresolved hold
Draft a2c34f25 · not reviewed
Recommend HOLD internal closeout. The server-supplied deterministic readiness gate is HOLD and says AI drafting cannot clear it. Its recorded reasons are: the current report needs exact professional review; report13/source3 does not cover the changed scope2; there is no delivery reference; there is no explicit client acceptance; and the remaining Northline support and retention handover is open or unreconciled. These reasons explain the hold; this draft does not independently decide or alter readiness.
NorthlineTXT
AI-prepared material; reviewed internally
A precedent selected for the actual question
Copy 83f3a5f0
The permitted precedent set is limited to owned sample firm methods; the knowledge search returned no other permitted entries. The closest fit is the Cross-case interview synthesis method, version 2. It fits because the present question is not whether a service should be launched, but how to compare selected role accounts while keeping a reported experience separate from a causal explanation. It transfers four usable disciplines: quote-linked candidate themes; visible source roles; a specific explanation of what any apparently contrary account challenges; and an explicit limit on prevalence, causation, demand and value claims.
NorthlineTXT
AI preparation and recorded human judgement
A correction turned into a candidate lesson
Copy 0f6da8a1
Human correction: classify the relationship as qualified, not opposing. The lead account narrows one proposed explanation; missing handover information; for two checked sample cases. It does not contradict the sponsor’s uncertainty over which version was active, and it does not erase the distinction between a file existing and a participant being able to identify the current version. The earlier model classification remains inspectable history; the reviewed relationship is a fresh, run-specific human judgement.
NorthlineTXT
AI-prepared exercise; human internal review
Practice material that makes the reasoning visible
Copy 33a6c8d3
Interpretation A: label the second account as opposing evidence because it says the file was complete. Interpretation B: label it as qualifying a missing-information explanation, while retaining it as compatible with the distinction between completeness and visibility. Interpretation B is the stronger reading. Completeness narrows a claim that absent material caused the question; it does not answer whether people could identify the active version. The first account supports the visibility theme. Neither account establishes how often either condition occurs or which condition caused the question.
NorthlineTXT
Actual AI preparation; human owner correction
A retrospective with a specific next action
Copy 15990741
Improvement action 1; Nadia, existing named owner: assess the scope-v2 change against the earlier scope-v1 report and record whether a revised internal working product is required. Test: a review must explicitly identify whether the residual-obligation preparation deliverable is represented; it must not imply access, retention, contractual, or client actions.
An interpretation the reviewer can challengeDOCX
Northline
- Contents
- An interpretation the reviewer can challenge
- Version
- Report 12 · source 2
- File
- DOCX
NorthlineTXT
Actual AI response; Maya’s clarity edits; internal review
A response that addresses the actual concern
Working copy 26a56d09
You asked why the sponsor passage was called counter-evidence and whether three authored accounts supported a recurrence claim. The earlier counter-evidence label was an evidence-classification error. The sponsor’s account describes uncertainty about the decision awaiting action and the next owner; it supports investigating that uncertainty. It does not demonstrate that approval delays caused repeated questions, nor does it oppose the theme.
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
Evidence; 02-client-sponsor.txt: I could not tell which version the team was using.
Reason and limits: Fresh method2 run still uses the same lead quotation as both support and counter-evidence. Human review distinguishes the claim being challenged from the theme itself. This is a new run-specific judgement, not an automatic carry-over of the earlier T1 correction. Three authored accounts establish no frequency, cause or demand.
A response that addresses the actual concernTXT
Northline
- Contents
- A response that addresses the actual concern
- Version
- Working copy 26a56d09
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI response; Maya’s clarity edits; internal review
A response that addresses the actual concern
Working copy 26a56d09
You asked why the sponsor passage was called counter-evidence and whether three authored accounts supported a recurrence claim. The earlier counter-evidence label was an evidence-classification error. The sponsor’s account describes uncertainty about the decision awaiting action and the next owner; it supports investigating that uncertainty. It does not demonstrate that approval delays caused repeated questions, nor does it oppose the theme.
The replacement is report 12, source 2. The project lead found the current brief in both checked handovers. That challenges a missing-information explanation for those two cases; it does not explain away the sponsor’s uncertainty about which brief was being used.
A reconciliation query, with the uncertainty intactTXT
Northline
- Contents
- A reconciliation query, with the uncertainty intact
- Version
- Working copy 7aa6ab2f
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI finance draft; human internal review
A reconciliation query, with the uncertainty intact
Working copy 7aa6ab2f
The supplied assertions reconcile deterministically to one invoice assertion, INV-NORTH-01, for AUD 100. They also contain a AUD 20 received-payment assertion, PAY-NORTH-01, followed by an exact AUD 20 reversal for that same payment. The payment’s net asserted effect is therefore AUD 0. The supplied reconciliation consequently reports matched receipt assertions of 0 and an asserted balance of AUD 100, labelled “No matching receipt.” No unmatched assertions or held reversals are supplied.
This is not a cash, billing, collection, or legal conclusion. The stated sample terms make invoice eligibility conditional on explicit acceptance of report12/scope1. The available acceptance material is a sample sponsor-receipt scenario and expressly does not establish an actual message, signature, acceptance, send, or payment. Accordingly, the actual contract condition and any real invoice eligibility remain unresolved.
A handover with named responsibilitiesTXT
Northline
- Contents
- A handover with named responsibilities
- Version
- Working copy 4f081531
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI checklist; human internal review
A handover with named responsibilities
Working copy 4f081531
Nadia, the accountable sample lead, owns receipt and internal review of the remaining handover. Elena, in the departing sample role, owns preparation: identify remaining clarification support, record the retention obligation, and identify permitted Northline-only material. Rowan is the named sample receiver. The stated 29 October 2026 date is an internal target, not a client promise.
Completed preparation is limited to the sample receiving record: Rowan acknowledged the Northline-only preparation checklist and named support/retention responsibilities, recorded by Nadia in an authored local scenario. That is receipt of preparation only. It does not verify an access grant, access revocation, retention period, deletion, or completion of a client duty.
A draft that cannot clear an unresolved holdTXT
Northline
- Contents
- A draft that cannot clear an unresolved hold
- Version
- Draft a2c34f25 · not reviewed
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI draft; Maya’s clarification; NOT REVIEWED
A draft that cannot clear an unresolved hold
Draft a2c34f25 · not reviewed
Recommend HOLD internal closeout. The server-supplied deterministic readiness gate is HOLD and says AI drafting cannot clear it. Its recorded reasons are: the current report needs exact professional review; report13/source3 does not cover the changed scope2; there is no delivery reference; there is no explicit client acceptance; and the remaining Northline support and retention handover is open or unreconciled. These reasons explain the hold; this draft does not independently decide or alter readiness.
A precedent selected for the actual questionTXT
Northline
- Contents
- A precedent selected for the actual question
- Version
- Copy 83f3a5f0
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
AI-prepared material; reviewed internally
A precedent selected for the actual question
Copy 83f3a5f0
The permitted precedent set is limited to owned sample firm methods; the knowledge search returned no other permitted entries. The closest fit is the Cross-case interview synthesis method, version 2. It fits because the present question is not whether a service should be launched, but how to compare selected role accounts while keeping a reported experience separate from a causal explanation. It transfers four usable disciplines: quote-linked candidate themes; visible source roles; a specific explanation of what any apparently contrary account challenges; and an explicit limit on prevalence, causation, demand and value claims.
Applied here, the method supports retaining two distinct candidate propositions: uncertainty about the current brief version, and uncertainty about an open decision or next owner. The project-lead account qualifies only a missing-information explanation in two sample cases because it reports complete handovers. It does not negate the separate account of version uncertainty. Likewise, the sponsor account of a waiting decision supports investigation of ownership visibility, but does not establish that approval delay caused repeated questions. No counterquote should be manufactured for themes where none is warranted.
A correction turned into a candidate lessonTXT
Northline
- Contents
- A correction turned into a candidate lesson
- Version
- Copy 0f6da8a1
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
AI preparation and recorded human judgement
A correction turned into a candidate lesson
Copy 0f6da8a1
Human correction: classify the relationship as qualified, not opposing. The lead account narrows one proposed explanation; missing handover information; for two checked sample cases. It does not contradict the sponsor’s uncertainty over which version was active, and it does not erase the distinction between a file existing and a participant being able to identify the current version. The earlier model classification remains inspectable history; the reviewed relationship is a fresh, run-specific human judgement.
Reason: a source can address a neighbouring proposition without challenging the theme itself. Semantic relationship analysis therefore asks “what exact claim does this quotation narrow?” rather than treating textual difference, exact quotation matching, or an older combined label as proof of contradiction. The same discipline applies to the sponsor’s waiting-decision account: it supports visibility of a decision and next owner, but does not prove that an approval caused a repeated question.
Practice material that makes the reasoning visibleTXT
Northline
- Contents
- Practice material that makes the reasoning visible
- Version
- Copy 33a6c8d3
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
AI-prepared exercise; human internal review
Practice material that makes the reasoning visible
Copy 33a6c8d3
Interpretation A: label the second account as opposing evidence because it says the file was complete. Interpretation B: label it as qualifying a missing-information explanation, while retaining it as compatible with the distinction between completeness and visibility. Interpretation B is the stronger reading. Completeness narrows a claim that absent material caused the question; it does not answer whether people could identify the active version. The first account supports the visibility theme. Neither account establishes how often either condition occurs or which condition caused the question.
Learner check: write one sentence in the form “This quotation [supports/qualifies/contradicts/is unclear about] [exact proposition] because …”; then write one separate sentence stating what it does not establish. A reviewer should be able to see that no causal, frequency, demand, or performance claim has slipped into either sentence.
A retrospective with a specific next actionTXT
Northline
- Contents
- A retrospective with a specific next action
- Version
- Copy 15990741
- File
- TXT
NorthlineDOCX
AI candidate; human semantic correction
An interpretation the reviewer can challenge
Report 12 · source 2
The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.
NorthlineTXT
Actual AI preparation; human owner correction
A retrospective with a specific next action
Copy 15990741
Improvement action 1; Nadia, existing named owner: assess the scope-v2 change against the earlier scope-v1 report and record whether a revised internal working product is required. Test: a review must explicitly identify whether the residual-obligation preparation deliverable is represented; it must not imply access, retention, contractual, or client actions.
Improvement action 3; human correction: Nadia is the accountable lead for the existing residual-obligation preparation dependency; Rowan is the recorded next owner after Elena. Confirm that assignment and its reopened verification state against the current dependency record before preparing the support, access-verification and retention-verification decision fields. The AI preparation omitted that dependency record, so its original missing-owner assertion is unsupported. Test: the handover identifies owners and outstanding verification questions without asserting provider grants, revocations, retention periods, deletion, or receiving-system completion.
Marlow
4 saved outputs
A briefing that distinguishes change from uncertaintyTXT
Marlow
- Contents
- A briefing that distinguishes change from uncertainty
- Version
- 19 Oct compared with 12 Oct 2026
- File
- TXT
MarlowTXT
Actual AI preparation; fresh internal review
A material-change assessment for review
12 → 19 October 2026
Observed change: R1, the decision to propose workstream-A mobilisation, moved from blocked because the required assurance record was not received to ready because it was reported received. The evidence text changed. This is a candidate for professional materiality judgement, not an automatic finding that the underlying assurance is valid, that authority exists, or that advice, a commitment, or a release should be rewritten.
MarlowTXT
Actual AI update; fresh internal review
A briefing that distinguishes change from uncertainty
19 Oct compared with 12 Oct 2026
Changed: R1 is classified changed. The assurance record is now reported received and the status is ready rather than blocked. This supports preparing the question whether mobilisation may responsibly be proposed, but does not approve release: validity and actual authority require review.
Unchanged: R2 remains open with no recorded client instruction; R4 remains open with no diary acceptance. The competent existing steering meeting and action register remain the process comparator, not proof of current operational continuity.
Uncertain: R3 remains unknown; validation was not observed and technical evidence is missing. The actual decision implications are therefore limited: the ordinary pre-read/meeting can prepare questions, while waiting for Nadia’s R1 evidence review, the sample client sponsor’s R2 instruction, the sample specialist reviewer’s R3 validation, and the sample programme lead’s R4 confirmation. A proposed exception brief remains an internal input, not existing delivery or rewritten issued advice.
A material-change assessment for reviewTXT
Marlow
- Contents
- A material-change assessment for review
- Version
- 12 → 19 October 2026
- File
- TXT
MarlowTXT
Actual AI update; fresh internal review
A briefing that distinguishes change from uncertainty
19 Oct compared with 12 Oct 2026
Changed: R1 is classified changed. The assurance record is now reported received and the status is ready rather than blocked. This supports preparing the question whether mobilisation may responsibly be proposed, but does not approve release: validity and actual authority require review.
MarlowTXT
Actual AI preparation; fresh internal review
A material-change assessment for review
12 → 19 October 2026
Observed change: R1, the decision to propose workstream-A mobilisation, moved from blocked because the required assurance record was not received to ready because it was reported received. The evidence text changed. This is a candidate for professional materiality judgement, not an automatic finding that the underlying assurance is valid, that authority exists, or that advice, a commitment, or a release should be rewritten.
Unaffected issues: R2 is classified unchanged and remains an undecided scope choice with no client instruction. R4 is unchanged and remains a proposed but unconfirmed meeting window. R3 is uncertain, not a change finding: validation remains unobserved and technical evidence missing. These issues may shape questions for the competent steering process, but do not establish changed contract scope, client demand, rights, payment, tooling, meeting acceptance, or programme outcome. Unknown remains unknown.
A service test compared with the existing processTXT
Marlow
- Contents
- A service test compared with the existing process
- Version
- Current internal preparation
- File
- TXT
MarlowTXT
Actual AI update; fresh internal review
A briefing that distinguishes change from uncertainty
19 Oct compared with 12 Oct 2026
Changed: R1 is classified changed. The assurance record is now reported received and the status is ready rather than blocked. This supports preparing the question whether mobilisation may responsibly be proposed, but does not approve release: validity and actual authority require review.
MarlowTXT
Actual AI preparation; human review and proposed next step
A service test compared with the existing process
Current internal preparation
Bounded internal test plan. End-client decision: which workstream commitments may responsibly be proposed for the next fortnight, which need a client decision, and which lack a verified evidence basis. The competent comparator is the existing monthly steering meeting and action register, with the four issue questions added manually to the ordinary pre-read. The proposed extra input is one versioned cross-period exception brief separating changed, unchanged and uncertain evidence, naming the responsible checker, and connecting each item to a decision. It does not replace the meeting or require software.
Included hypothetical per-cycle planning costs are preserved. Existing: Reviewer 0.75 hour at AUD180 = AUD135; Associate 1 hour at AUD90 = AUD90; total AUD225. Proposed: Reviewer 1 hour at AUD180 = AUD180; Associate 3 hours at AUD90 = AUD270; Upkeep 0.5 hour at AUD120 = AUD60; Tools one cycle at AUD25 = AUD25; total AUD535. Incremental planning cost: AUD310. Included items are only those listed. Setup, integration, overhead, support, extra assurance, tax and contingency are excluded or unverified. These are not a fee, savings, spend, capacity release, purchase, or approval; the tools allowance is not a purchase obligation.
An account review without an automatic upsellTXT
Marlow
- Contents
- An account review without an automatic upsell
- Version
- Current internal preparation
- File
- TXT
MarlowTXT
Actual AI update; fresh internal review
A briefing that distinguishes change from uncertainty
19 Oct compared with 12 Oct 2026
Changed: R1 is classified changed. The assurance record is now reported received and the status is ready rather than blocked. This supports preparing the question whether mobilisation may responsibly be proposed, but does not approve release: validity and actual authority require review.
MarlowTXT
Actual AI preparation; human internal review
An account review without an automatic upsell
Current internal preparation
Next-scope hypothesis: Nadia and Maya could internally compare an improved ordinary pre-read containing the same four questions with a versioned exception brief. The relevant question is whether the latter adds a distinct actionable decision input between meetings; it may instead show that the ordinary pre-read is sufficient. The human next step is internal review to defer, refine the comparison, stop it, or prepare a separately scoped proposal. There is no automatic upsell, contact, meeting request, or client action.
Birchwell
2 saved outputs
An internal proposal that carries its scopeDOCX
Birchwell
- Contents
- An internal proposal that carries its scope
- Version
- Internal proposal 2
- File
- DOCX
BirchwellTXT
Human-entered assumptions; deterministic comparison
A delivery plan with role constraints
Plan 3 · scope 4
Analyst: available 24h; baseline 8h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Reviewer: available 6h; baseline 2h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Case-equivalent capacity 3 → 1.5; these are not scheduled/completed engagements.
BirchwellDOCX
AI preparation; human scope, estimates and internal decision
An internal proposal that carries its scope
Internal proposal 2
Which first onboarding process test should Birchwell choose after a checklist desk review and one internal workshop?
A short internal options briefing: current-process observations from the supplied materials; comparison of (1) retaining/tightening the existing meeting and project-folder process and (2) adding a form; discovery hypotheses; first-test decision criteria; and explicit exclusions and unresolved acceptance conditions.
No interviews, interview access, external contact, handover-file access, implementation or dashboard build. No claims of credentials, insurance, conflict clearance, resource availability, client agreement, budget, agreed fee, delivery date or award. Human estimates below are internal planning only.
A delivery plan with role constraintsTXT
Birchwell
- Contents
- A delivery plan with role constraints
- Version
- Plan 3 · scope 4
- File
- TXT
BirchwellDOCX
AI preparation; human scope, estimates and internal decision
An internal proposal that carries its scope
Internal proposal 2
Which first onboarding process test should Birchwell choose after a checklist desk review and one internal workshop?
BirchwellTXT
Human-entered assumptions; deterministic comparison
A delivery plan with role constraints
Plan 3 · scope 4
Analyst: available 24h; baseline 8h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Reviewer: available 6h; baseline 2h/case; revised 4h/case; 1 case(s) need 4h; overload 0h.
Case-equivalent capacity 3 → 1.5; these are not scheduled/completed engagements.
Harbour
1 saved output
Reviewed operational diagnosticDOCX
Harbour
- Contents
- Reviewed operational diagnostic
- Version
- Report 7 · source 1
- File
- DOCX
HarbourDOCX
AI preparation; human wording and exact-version review
Reviewed operational diagnostic
Report 7 · source 1
For 26 October 2026, 300 available hours at an estimated five hours per job model 60 jobs; this is not measured throughput. The confirmed-only comparison uses 60 jobs. The planning register still contains 80 jobs, including 20 provisional jobs dependent on client access. If none of those provisional jobs release during the week, the confirmed-only comparison remains 60; if all release, the potential workload is 80 against the same 60-job model. The planning register remains 80 in both scenarios. These conditional comparisons do not establish delivery readiness, spare capacity, staffing need or a commitment. Confirm actual access-release dates, validate job mix and measured effort, and compare scheduling and service scope before deciding.
The effort input is an estimate. Validate the period, job mix and available options before any commitment. This comparison does not establish staffing viability or guaranteed delivery.