Deadline Risk Note Analyzer

How Deadline Risk Note Analyzer works

Press Load model once: your browser downloads Gemma 4 E2B instruction-tuned (web build) (2.0 GB) from this site and keeps it in its cache. Then add your text and press Analyze locally. The model runs on this device using your graphics card, so nothing you enter is sent to a server. Until the model is loaded, or if your device cannot run it, the tool falls back to a simple keyword check and labels the result as the fallback.

Gemma 4 E2B instruction-tuned (web build) is a small open language model from Google. The tool sends it the instruction below plus your text, asks for a JSON answer with fixed fields, and shows each field as a card. It runs at temperature 0, so the same input gives the same answer on the same device, though different graphics cards can word it slightly differently.

Inputs longer than 6,000 characters are cut to that length before they reach the model, and the result says so. The model only sees what you paste: it does not look anything up.

The instruction the model gets

You read a project status note and pull out deadline risks. Copy the deadline and every percentage, date and duration exactly as written; do not calculate slack, delays or new dates. List risks only from what the note says.

What it returns

• Deadline: The committed date or milestone exactly as written, or an empty string if none.
• Risks: Each risk the note mentions: late work, missing people, unstarted steps, blocked dependencies.
• Dependencies: Teams, vendors, approvals or tasks the deadline depends on.
• Unknowns to chase: Things the note leaves unclear that someone should confirm, such as owners or start dates.

Worked example

The model's output for the built-in sample, recorded on a desktop browser. Your run may word things slightly differently.

Deadline note: Beta promised July 31. API integration is 70% done, design assets late by 5 days, legal review not started, one engineer out next week.

Deadline

July 31

Risks

design assets late by 5 days legal review not started one engineer out next week

Dependencies

API integration

Unknowns to chase

owner of design assets start date for legal review

The model

The files are served from this site, versioned so a cached copy is never stale. Nothing is fetched from a third party while you use the tool.

Limitations

• Small language models make mistakes: they can miss an item, merge two, or state something more confidently than the text supports. Check the result against your input before you rely on it.
• It needs WebGPU and about 8 GB of memory, so it is offered on desktops and laptops, not on phones and tablets. Devices that cannot run it get the keyword fallback, clearly labelled.
• Results describe the input you gave, not the real-world situation behind it. Review them yourself before acting.

Good uses

• Triage calendar and scheduling notes before deeper review
• Prepare consistent labels for repeat workflows
• Reduce manual sorting on small batches
• Keep sensitive drafts in the browser preview