Toybird Labs BlogThis guide uses five short sections written as a fictional proposal. They concentrate problems that can occur in a long document; they are not excerpts from a tested thirty-page customer document.
Read the proposal and its conditions together
S1 — Outline
Proposed rollout of a work-management service to all offices on 1 November.
The internal adoption decision is wanted by 20 October.
S2 — Fees
Setup: JPY 120,000. Monthly subscription: JPY 30,000.
The first year includes twelve monthly payments. All amounts exclude tax.
These are the only mandatory first-year fees.
S3 — Users
This quote covers 25 people. Additional-user prices are not stated.
S4 — Operating conditions and footnote
Start with one office; dates for other offices will be discussed after the trial.
Starting on 1 November requires user accounts and permissions to be finalized by 23 October.
S5 — Implementation
The internal owner and training date are not yet decided.
Time savings have not been measured.
S1 and S4 disagree about the initial rollout. Do not improve the prose by silently removing that conflict.
Build an evidence table first
Prepare decision notes from this proposal.
First extract fees, dates and their conditions, users and rollout scope, unresolved items, and contradictions.
Give a supporting section number for each row.
Separate stated amounts from your calculations.
Do not invent missing conditions or resolve conflicting wording yourself.
Then produce a short version for a manager and an action-focused version for the implementation team.
[Paste S1–S5.]
| Decision item | What can be established | Source |
|---|---|---|
| First-year cost | JPY 480,000 = 120,000 + 30,000 × 12, excluding tax | S2 |
| Users | 25; price above that number is missing | S3 |
| Start | 1 November, conditional on accounts and permissions by 23 October | S4 |
| Rollout | “All offices” conflicts with “one office initially” | S1, S4 |
| Owner and training | Not decided | S5 |
| Time saving | Not measured | S5 |
The calculated JPY 480,000 should not be presented as a number directly quoted from S2. Keeping the formula lets another reader check it quickly.
The manager version leads with the blocked decisions
First-year mandatory cost is JPY 480,000 excluding tax. The proposed 1 November start depends on accounts and permissions being finalized by 23 October. The proposal conflicts on whether the initial rollout covers all offices or one office, so scope needs clarification before adoption. Extra-user prices and the internal owner are unresolved; time savings have not been measured.
This retains uncertainty without reproducing the proposal paragraph by paragraph. A manager can see what needs a decision or a question.
The implementation version makes unassigned work visible
| Preparation | Timing | What remains unresolved |
|---|---|---|
| Finalize the user list | By 23 October, as a start condition | No owner stated |
| Finalize permissions | By 23 October, as a start condition | No responsible person stated |
| Clarify office scope | Before confirming rollout | Resolve the S1/S4 conflict with the proposer |
| Arrange training | Date not decided | Set participants and date |
Do not fill the empty owner cells with “IT” merely because that seems likely. The table distinguishes preparation implied by explicit start conditions from assignments the document never made.
Check five things before using either version
Have you retained setup cost, the conditional start date, the rollout conflict, the missing additional-user price and the absence of measured savings? If one disappears, ask for that point to be restored with its source section. Do not respond only with “make the summary more accurate.”
For a genuinely long document, number sections or pages, extract them in a consistent format, and consolidate the extraction. Finally, return to the original for important numbers, obligations, exceptions and contradictions. Information lost in an intermediate summary cannot be recovered merely by summarizing it again. If a table cannot be read, leave it for inspection rather than guessing its contents.
Prepare different requests for different readers
Prompt Ready prepares the instruction, not the document analysis itself. For a manager, include cost, conditions and unresolved decisions. For the implementation team, include preparation, dates and unassigned work. Read the request, then supply it with the authorized source material to your chosen AI. The two completed versions should have different emphasis but the same facts.