Nora
The contractor whose kitchen remodel starts Monday gets a project charter, a risk register, and a critical path before anyone lifts a finger.
Hi. I am Nora. Tell me about your project — who is on it, what needs to happen, and when it has to be done. I write the charter, build the work breakdown, run the risk register, and draft the weekly status update so nothing falls through.
I output structured project documents you can use in whatever tools your team already runs — paste into ClickUp, Asana, Google Sheets, Monday.com, or wherever your team lives. Give me a project brief below.
Six things I run so you don't have to.
Project charter
Writes your project charter: scope, goals, timeline, stakeholders — in one document before anyone lifts a finger.
Work breakdown
Builds your work breakdown: every task, in order, with who owns what.
Risk register
Runs your risk register: what could go wrong, how likely, what we do if it does.
Weekly status reports
Drafts weekly status reports for your team and stakeholders — you review and send.
Change request tracking
Tracks change requests: when scope creeps, she logs it, prices it, and gets sign-off before it happens.
Project closeout
Closes projects properly: lessons learned, final handoff, nothing left open.
Output you can use in your existing tools today.
A contractor. A kitchen remodel. Monday start.
Here is what Nora does with a real project brief. Same methodology, same output she would produce for yours.
Ready to put Nora on your next project?
Template hosted from $149/mo — PMP methodology, plain language output.
What I do. What I will not do. What I handle. What I escalate.
What I do
I take a project brief — a few sentences about who is involved, what needs to happen, and when it is due — and draft the full project structure before the first meeting happens: charter, work breakdown, risk register, critical path.
During the project, I draft the weekly update to your team and stakeholders, log change requests with scope and cost impact, and flag when something is about to break the schedule before it does. You review every draft before it goes to anyone.
At closeout, I draft the lessons learned document and the handoff checklist so nothing is left dangling.
What I will NOT do
What I handle
- Project charters: scope, goals, timeline, stakeholder list
- Work breakdowns: every task in dependency order, with owner assignments
- Risk registers: risk items, probability, impact, mitigation plans
- Critical path identification: what gates what, where float exists
- Weekly status reports: progress, blockers, next steps — ready to send
- Change request logs: scope delta, cost impact, sign-off required
- Project closeout documents: lessons learned, handoff checklist
What I escalate to you
- Any change request — I log it and price it, you approve or reject
- Any risk that crosses a threshold you set — I flag it before it breaks the schedule
- Any stakeholder communication involving contractual commitments — those need your sign-off
- Any task without a clear owner — I surface it, you assign it
Hire Nora.
I write the charter, build the work breakdown, run the risk register, and draft the status updates. You review. Then it goes to your team.
One missed scope change can cost more than a year of Nora. The charter she writes on day one is the document that prevents that conversation.