The short answerA tender methodology explains how you will deliver the work. A strong one follows the buyer's scope in order and covers your approach, the people and equipment, the program, how you will manage risks, quality, safety and the environment, and how you will communicate and report. Make it specific to this site and scope, not a generic company manual.
A section by section structure
- Understanding of the scope and the buyer's goals
- Approach to each part of the work, in the scope's order
- Resources: people, equipment, subcontractors
- Program and key milestones
- Risks and how you will manage them
- Quality, WHS and environmental management
- Communication and reporting
- Handover or transition, where relevant
Make it specific
- Name the site, the hours, the access and the constraints in the tender.
- Show numbers: crew sizes, frequencies, response times.
- Tie each risk to the actual site or work.
- Cut anything that could be pasted into any tender.
A methodology checklist
- Follows the scope in the buyer's order
- Names the site and its constraints
- States crew sizes and frequencies
- Shows the program and milestones
- Lists real risks with controls
- Explains quality checks
- Explains WHS for this work
- Explains reporting to the client
Use simple visuals
A table of tasks and frequencies, a simple flow of how a request is handled, or a site plan showing access and set down areas can replace pages of text. Check that diagrams count within page limits.
A methodology structure that scores well
- Understanding. Show you know the site, the users and the risks in this job.
- Approach. Step by step, how you will deliver each part of the scope.
- Resources. People, plant and hours, matching your price.
- Programme. Key dates and hold points.
- Risks. The main risks and what you will do about each one.
- Quality and reporting. How the buyer will know the work is done right.
Follow the buyer's headings if they give them. Their structure always beats yours.
Questions
What is the difference between a methodology and a program?
The methodology explains how you will do the work. The program shows when, as a timeline of activities and milestones.
Should I include diagrams?
Yes, if they help and the buyer allows them. A simple flow or site plan can explain more than a page of text.
How long should a methodology be?
Within the buyer's limit, and in proportion to its weighting. A heavily weighted methodology deserves real depth.