Set the reporting window
Give Nema the previous approved update, current task export, reporting dates, and the project Slack channel. Define the status fields and any milestone terms the team uses. The previous update matters because readers need to know what changed, not receive the full plan again.
State the audience and level of detail. A working-team update and an executive summary answer different questions.
Report movement rather than activity
Ask Nema to focus on completed milestones, changed dates, new blockers, resolved dependencies, and decisions. A long list of comments does not show whether the project moved.
Each important statement should point to the task record or channel decision supporting it. If a task system says complete but the owner reports unfinished review, present the conflict instead of choosing one source silently.
Make blockers actionable
A blocker needs an affected outcome, the missing input, a responsible owner when one is known, and a decision or date. "Waiting on design" is weaker than "The onboarding email cannot enter review until the product image is approved; the design owner has not confirmed Friday."
Nema should leave unsupported owners or deadlines blank and ask the project lead to fill them. This keeps the update from creating commitments by accident.
Review in the project channel
Post the draft where contributors can correct it. The project owner resolves status conflicts, chooses which risks to escalate, and confirms the final wording. Nema can then produce a shorter version for stakeholders who do not need the working detail.
A scheduled routine can prepare the same draft each week after the input path and definitions are reliable. The owner still reviews material changes and sensitive details.
Start with one workstream
Choose a project with a recent approved update and a clean task export. Ask for changes only. Verify every blocker and decision with its owner. This first run reveals stale task fields and informal conventions that should become explicit guidance.
Questions from project teams
What if Slack and the task tracker disagree?
Nema can show both statuses and their timestamps. The project owner decides which is current and updates the source of record.
Can Nema assign owners?
It can carry forward owners named in the source. It should ask when a new item has no confirmed owner.
Can the update run every Friday?
Yes, after the team verifies the inputs and report shape. Each run should show its reporting window and data freshness.