Every phase, every deliverable, every team ritual — organized in one shared space. Manage internal work invisibly, guide clients transparently, and close every engagement with clarity and confidence.
Consulting engagements don't fail because of bad work. They fail because of how the work is managed.
Work lives in email threads and chat messages. When someone gets sick, joins late, or gets pulled onto another project, context evaporates. There's no system — so scaling the team, onboarding someone mid-engagement, or simply picking up where someone left off becomes its own project.
Teams spend more time figuring out what comes next and who owns what than actually doing the work. Without a shared structure, every engagement gets reinvented from scratch — and the same coordination overhead repeats every time.
And the things that hold teams together — rituals, shared expectations, how decisions get made — are never written down anywhere. They exist in someone's head, or they don't exist at all.
This process covers the full consulting engagement lifecycle — from the moment you first speak with a potential client to the moment you hand off the final deliverables and close the project. Every phase has its own tools, its own visibility rules, and its own deliverables. They're designed to run sequentially but adapt to your engagement type.
The full process template is available in Nova's process library. Duplicate it, customize it to your methodology, and run it with your first client in under an hour.
Before any work begins, you need to understand who the client is, what they actually need, and what success looks like to them. The Discovery Questions session is a structured survey sent to the client — or to the entire client team — and it's designed to be completed collaboratively, so everyone on their side can see each other's answers in real time.
If the engagement involves more than one person on the client side, send the discovery session link to all of them. Each person answers independently and can see others' responses as they come in. Diverging answers are conversation starters — not problems to smooth over.
The default question set covers company context, goals, competitive position, constraints, stakeholders, and success criteria. Adapt it to your methodology — remove questions that don't apply, add ones that do. The structure is yours to shape.
After the client submits, your team reviews the answers in the internal prep section. This is where you note patterns, tensions, and open questions before you get on a call. A well-prepared team asks better questions.
Instead of emailing a PDF and waiting for a reply, the Proposal & Contract session puts the document and the review process in the same place. The client reads, annotates, asks questions, and approves — all in one structured flow. If the client is a team, every member can see each other's notes and concerns before anyone signs.
Download the proposal, take your time to read it, and sign it once you have reviewed all the details. Then attach the signed copy here. After that, move to the next step to approve and notify the team.
Attach the proposal directly in the session. Clients download, annotate, and re-upload the signed version — no email chains or version confusion.
If the client is a team, all members can see each other's approval status and notes. Consensus surfaces naturally before anyone commits.
Three clear responses: Approve, Request changes, or Decline. Notes can be added to any response. Nothing is left ambiguous.
Once the client approves, the team uploads the countersigned copy. Both versions are stored in the session for the life of the engagement.
The kickoff call isn't just an introduction meeting — it's the moment you establish the working relationship, confirm the plan, and give the client confidence that they chose the right team. The Kickoff session in Nova runs on a shared whiteboard so both teams are literally looking at the same thing: the phases, the deliverables, the timeline, and the norms.
Review the discovery answers as a team, align on the engagement plan, identify any open questions, and confirm who leads each phase. Assign a note-taker for the call. Prepare a simple visual summary of phases and deliverables to share on screen.
Walk the client through the phases, deliverables, and timeline. Use the shared whiteboard to make the plan visible and tangible. Confirm roles and communication norms — how often you'll meet, how decisions get made, how feedback gets submitted. End with open questions, not a presentation.
Immediately after the call, log the key decisions made, open questions raised, and action items for both sides. These go into the meeting log and are visible to both teams. A clean post-kickoff note builds trust — it shows you were listening and are already in execution mode.
The execution phase is where the actual work happens. This is predominantly internal — clients don't need to see every task, every blocker, or every conversation your team is having about how to approach a problem. The process gives you structured tools for managing work, and keeps it in the same workspace as everything else.
Add any new decisions made, any changes to the plan, or delays that require adjustments and coordination among all affected team members.
The default template. Add tasks, assign owners, set due dates. Full team visibility with completion tracking. Simple and effective for most engagements.
Swap the to-do list for a kanban board to manage work in columns: backlog, in progress, review, done. Available as an alternative template from the library.
Organize tasks by engagement phase. Each phase gets its own section with its own team lead, deliverable checklist, and reviewer assignment.
Built-in structured log for key decisions, plan changes, and delays. Every log entry has a date, owner, and impact note — searchable for the whole team.
Over the course of an engagement, the accumulated context — decisions made, things promised, problems raised and resolved — is one of your most valuable assets. The meetings section gives every session, every note, and every decision a permanent home in the workspace. Nothing gets lost in email threads or chat messages.
The most valuable habit in this system: before anyone leaves the meeting, the note-taker posts the key decisions, open questions, and next actions in the meeting log. It takes five minutes and it prevents weeks of ambiguity. This is the discipline that makes everything else work.
The log has three entry types: decisions (things that change the direction or scope of work), wins (positive signals worth remembering), and delays (anything that moves the timeline with a note on why and what the impact is). This distinction makes retrospectives and client updates much easier to write.
If you're sending regular status updates to the client, the meeting log is your source of truth. Filter by the last two weeks, pull the decisions and wins, note any delays, and you have a status update in five minutes — accurate, specific, and evidence-based.
Rituals aren't ceremonies — they're the recurring structures that preserve team alignment when the work gets complicated. This section of the process is yours to define. The defaults below are the ones most high-performing consulting teams use, but every team is different. Adapt to your culture, your cadence, and the nature of the work.
Review deliverable progress against the plan, update the decision log, assess risks, and prepare the client update. This feeds directly into client communication.
What's working, what isn't, what needs to change. A structured team retrospective that protects quality and prevents the slow drift that degrades most engagements over time.
The first week of the engagement, book every ritual for the full engagement duration on everyone's calendar. This sounds administrative but it's one of the highest-leverage actions in the entire process. A ritual that isn't booked gets skipped. A skipped ritual means drift.
Each ritual type has a pre-built template in Nova with a default agenda and sections for notes, decisions, and actions. Run from the template — not from memory. Templates reduce prep time, increase consistency, and make it easy to spot when something's off-track.
Most engagement problems trace back to unclear ownership. The Roles & Responsibilities section in Nova shows two simple roles for every activity — Lead and Collaborator. Assign real names, share it at the kickoff, and every team member knows who to go to at every stage of the engagement.
| Engagement Activity | Lead | Collaborator |
|---|---|---|
| Discovery survey | Lead | Collaborator |
| Proposal & contract | Lead | — |
| Kickoff facilitation | Lead | Collaborator |
| Deliverable production | Lead | Collaborator |
| Internal review | Lead | Collaborator |
| Client feedback session | Lead | Collaborator |
| Final sign-off | Lead | — |
| Handoff & closure | Lead | Collaborator |
A strong close is as important as a strong start. The Handoff & Closure section gives your team a structured closing sequence — so nothing gets forgotten, access gets properly handed over, sign-off is documented, and the client leaves with everything they need to succeed without you.
The team reviews every deliverable against the original scope and the changes logged during the engagement. Confirm nothing is missing, confirm final documentation is complete (project summary, deliverable list, change log if applicable, recommendations for future steps).
A structured session to walk through everything delivered, how to use it, and what happens next. Include a live demo or walkthrough where applicable. End with formal sign-off — verbal in the session, documented in the workspace.
Collect sign-off from each key stakeholder on the client side — not just the primary contact. Each person uses the approval flow: approve, request changes, or sign off with a note. All approvals are logged and stored in the workspace with timestamps.
Transfer all credentials, tool access, and permissions to the client. Document what was transferred, who received it, and when. Remove team access from client tools if applicable. This step is frequently overlooked and creates friction months after the engagement ends.
After the client is fully closed out, the team runs a final retrospective: what worked, what didn't, what would we do differently. This is how methodologies improve over engagements. Document key learnings in the team knowledge base for use in future processes.
The complete Client Engagement Process is available as a customizable template in Nova's process library. Duplicate it, adapt it to your methodology, and run it with your team today.
Contact our team for hands-on guidance adapting this process to your consulting methodology. We'll help you configure the template, set visibility rules, and run your first engagement using it.