How an engagement works from brief to handover
Here is what happens at each stage of working with us, and what we ask of you.
The short answer
An engagement moves through six stages: brief, fit check, written scope, set-up, delivery and handover. Each stage ends with something you can read and approve, so you always know what has been agreed and what remains open.
The scope is set in writing before work starts. It names who leads, what is included and excluded, and how changes are handled. Dates and durations depend on your event and are set in that scope.
The six stages
| Stage | You do | The project lead does | You receive |
|---|---|---|---|
| 1. Brief | Share what is decided and what is open | Reads the brief and notes the gaps | Confirmation of what has been understood |
| 2. Fit check | Answer questions on decision owners, dates and suppliers | Assesses whether the support level suits the situation | A recommended support level, or a note that another route fits better |
| 3. Written scope | Review and approve | Writes scope, exclusions, responsibilities, review points and fee basis | A scope document and a quotation for approval |
| 4. Set-up | Name decision owners and share files and contacts | Builds the timeline, decision log, action list and supplier requirements | The working documents and the reporting format |
| 5. Delivery | Decide on dates and attend review points | Keeps actions moving, coordinates suppliers, reports progress, raises scope changes | Regular progress reports and an updated decision log |
| 6. Handover | Receive and confirm | Closes open items, assembles files and walks through them | Handover documents your team can continue from |
What a brief should contain
A brief can start incomplete. It helps most when it separates what is decided from what is not. The event brief builder produces an editable version you can send, with unknown dates and headcount left as unknown.
Fit check: the right level of support
A fit check can end with a recommendation to do the work yourselves, use a lighter level of support, or add more. Support is recommended only where it makes a clear difference.
Events outside Kuala Lumpur, Selangor and the Seremban area, including Nilai, follow the same steps. Planning and project management are delivered remotely, and on-site support and travel can be arranged when needed, subject to availability, agreed scope and costs. See areas and on-site arrangements.
Changes during delivery
Plans change. When a request falls outside the written scope, the project lead states the change, its effect on the work and the fee basis, and waits for your approval before proceeding.
Changes to the programme, budget or supplier choice are your decisions. They are recorded in the decision log with the date and who approved them. See fees, scope and quotations.
Reporting and decisions
- A status report in the agreed format and frequency: done, due next, at risk, decisions needed.
- A decision log: what was decided, by whom, when and what it affects.
- An action list with an owner and a date against every item.
- A short agenda before each review point, so decisions are ready to be taken.
Handover
Handover is part of every scope. It covers contacts, decisions made, supplier files, outstanding items and next steps, in a form that survives staff changes. The handover pack builder shows the shape.
Worked example · Fictional example
A fictional engagement from brief to handover
Fictional organisation, dates and durations, for illustration only.
A fictional chemical engineers' association sends a brief for a two-day conference in Selangor. The date window is set, the programme is partly drafted and no venue has been chosen.
The fit check recommends project coordination with the programme left to the committee. The written scope names the lead, lists the review points, excludes technical production and registration system operation, and states that a change in track numbers will be priced as a scope change. At the close, the committee receives the decision log, supplier files and a list of three items still open, each with an owner.
Use this yourself
Brief outline to send before a fit check
Answer what you can. Write 'not decided' where that is the true answer.
- Event type and purpose in two lines.
- Audience and approximate size, or 'unknown'.
- Date window, or 'not decided', and dates to avoid.
- Area or venue, if chosen.
- Who approves the programme, the budget and the suppliers.
- Suppliers or sponsors already appointed or promised.
- What your team will do itself.
- Support you are weighing: written plan, project lead, embedded manager, or not sure.
- Documents available: previous programme, budget, supplier contracts.
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have a written plan, named decision owners and capacity.
- You only need a document reviewed.
- The event is small and your team has run it before.
Outside planning help earns its fee when
- Nobody holds the dates, supplier handovers and decisions together.
- You need a scope in writing to get approval for outside support.
- You want a record that survives staff changes.
Ready to send a brief?
A project lead can read your brief, ask the fit-check questions and come back with a recommended level of support and what the written scope would need to say. Send the brief outline above, with the open items marked.
Questions organisers ask
Is there a cost for the fit check?
Any cost for early conversations is stated in writing before work starts. Fees for the work itself are quoted per brief. See fees and quotations.
Can I stop after the written plan?
Yes. The Event Blueprint is a complete deliverable, and you can execute from it yourselves.
What if the project lead is unavailable during delivery?
Continuity is described in the written scope. See continuity and backup arrangements.
Who owns the documents produced?
You do. They are delivered in the handover so your team can continue without outside help.
Related resources
Content record: Written by the EventConsultant team to our editorial rules. Sources are listed on pages that rely on them.