Apply for EDGE through the Business Grants Portal using your company’s authorised staff and Corppass access. First select the relevant activity, confirm its requirements and assemble the required project and vendor documents. Review the entire submission for consistency, then manage delivery and claim evidence against the approved terms.
A good application allows someone outside the business to understand what you need, what will be delivered and why the cost makes sense. The same structure also helps your team run the project. Prepare the application as the beginning of an evidence trail, so the final claim can be assembled from records created during normal delivery.
What to take away
- Use the selected activity’s document list and preserve one consistent version of the project scope.
- Give authorised company staff ownership of submissions and portal follow-up.
- Read the approval terms before delivery and collect evidence as work happens.
Confirm the activity before drafting the application
Write the intended business outcome in ordinary language, then identify the EDGE activity that supports the corresponding work. Read its supported costs, exclusions, deliverables and duration together. A proposal should not be built around the headline percentage while the detailed conditions are left until the end.
Save a working checklist of the requirements relevant to your project. Include any vendor qualifications, package identifiers, location evidence or projections the activity asks for. Note unresolved interpretation questions and clarify them before a supplier starts work. Do not assume that the documentation required by an earlier EDG, PSG or MRA application will be the same.
For a multi-part business plan, separate the activities and explain their relationship internally. Keep each application focused enough that its costs and outputs can be assessed independently. A shared business objective does not justify placing unrelated deliverables in a single application. Establish the boundaries first, then ask vendors for proposals that accurately reflect the work.
Write a project brief that connects need, work and result
Begin with the current situation. Describe the process or capability gap and give enough evidence to show its importance. Follow with the proposed work, the specific outputs and the expected improvement. The logic should be visible without promotional language. A reader should understand why the project is being proposed now and how the business will use its results.
For an illustrative maintenance company, the problem might be inconsistent job costing. The proposed work could analyse completed jobs, identify cost drivers and establish a quoting framework. The expected result is more consistent pricing and a clearer view of margins. This is easier to assess than an unsupported promise to transform profitability.
Explain projections using assumptions rather than presenting them as certain results. Show the starting point, the mechanism of improvement and the factors outside your control. If a revenue estimate depends on additional sales capacity, say so. Keep the project proportionate to the company's resources and avoid stretching the scope merely to reach a larger funding amount.
Make the quotation and application describe the same project
Check the supplier's legal name, the applicant's details, the package or service description, quantities, prices and delivery period. The scope in the quotation should match the scope entered in the portal. Remove ambiguous descriptions such as complete business package when the underlying tasks can be specified. Clear pricing helps both assessment and later invoice reconciliation.
Request a breakdown that reflects the work. Consultancy might be organised by phase and deliverable; software might be organised by licence, implementation and training; equipment might require unit details and deployment information. The required format varies by activity. Do not invent a universal three-quotation rule, but still undertake a sensible comparison of value and capability.
Keep commercial terms alongside the grant documents. Record renewals, exclusions, ownership, service levels, cancellation terms and payment milestones. A grant review does not replace procurement judgment. Before signing or paying, confirm the activity's rules on project commencement and commitments, including any explicit exception. Preserve earlier versions when a quotation changes, with a clear record of which version was submitted.
Every stage should describe the same project and connect to evidence from the previous stage.
Prepare company access and assign a submission owner
Check Corppass access early. The relevant company staff should have the Business Grants Portal roles needed to prepare and accept submissions. Test access while there is time to resolve account or role issues. A deadline is a poor moment to discover that the only employee with access has left or is unavailable.
Applications, change requests and claims must be submitted by the applicant's authorised employees or staff. Consultants and vendors can help prepare information, but the company should understand and control what is declared. Keep access credentials within the company's own controls. Assign an internal backup who knows where the current documents and correspondence are kept.
Set a final internal review before submission. Finance checks amounts and payment assumptions; the project owner checks scope and dates; management confirms the expected business result. This review should resolve contradictions rather than add more presentation. The person submitting should be able to explain every declaration and identify the evidence supporting it.
Submit accurately and manage clarification requests
Work through the portal using the final document set. Check that attachments are readable, filenames are intelligible and the totals reconcile. Review the business name, selected activity, vendor, project dates and contact details once more. Save the submission reference and the version of the information actually provided.
Monitor the portal and the nominated email account for requests. Route questions to the person who owns the relevant facts and answer them directly. If a question concerns an apparent inconsistency, explain the difference and provide the correcting evidence. Avoid sending a new proposal that quietly changes the project without addressing what was asked.
Processing time depends on the activity; a generic promise of approval within a fixed number of days is unreliable. If a supplier deadline is approaching, separate the commercial decision from the grant outcome. Submission does not guarantee funding. Document whether the business is willing and able to take the cost risk before it makes a commitment while assessment remains outstanding.
Read the Letter of Offer before launching delivery
When an application is approved, review the Letter of Offer and complete the required acceptance. Compare the approved amount, costs, deliverables and qualifying period with your intended plan. Resolve any misunderstanding before issuing instructions based on an assumption that the entire original proposal was accepted unchanged.
Translate the approval into a working delivery checklist. Assign an owner to each output and identify the evidence that will demonstrate completion. Put the project end date and claim deadline in a shared calendar, with earlier internal review dates. Ask the vendor to confirm that its delivery schedule supports these obligations.
Current EDGE change requests are limited to project-end and claim-due dates, subject to approval. Vendor changes are not a routine amendment: the published process calls for termination and a new application before proceeding with or paying the replacement vendor. Treat scope and vendor decisions as important commitments. If circumstances change, obtain specific guidance before assuming that an email agreement with a supplier preserves grant support.
Build the claim file while the project is running
Create separate folders for delivery evidence, invoices, payment records and approval correspondence. Use consistent references so a reviewer can connect each expense to its supplier, payment and approved work. Capture completion evidence when it is available rather than relying on a final week of reconstruction.
For a system deployment, retain the required identifiers and evidence of the approved functions. For consultancy, keep the completed reports, working outputs and records showing that the agreed work was delivered. The precise documents depend on the activity and approval. A photograph or attendance sheet is useful only when it proves something relevant to the required deliverable.
Before closing the project, reconcile the final cost list and confirm that all required outputs are complete and expenses fully paid. EDGE accepts a single final claim. Check that no approved item or necessary document has been overlooked. Claims open on 1 November for specified digital and equipment activities and 1 December for other activities. Include this launch timing in early project cash planning.
Review the final claim as an explanation of completed work
Ask a colleague who was less involved in delivery to review the claim file. They should be able to follow the story from approval to completed output, invoice and payment. Missing links often become obvious to a fresh reader. Check that any required translations or expense verification documents are included.
Confirm the company's disbursement details and monitor follow-up requests after submission. A submitted claim is not the same as an approved payment. Keep the project owner available to answer questions until the review is complete, and retain the records according to the applicable requirements.
Finally, close the operational loop. Record what improved, what staff still need and who will maintain the new capability. The grant process ends with a claim outcome; the business project should continue producing value. A concise internal handover helps prevent a completed system, report or framework from becoming unused material once the project team returns to daily work.
Frequently asked questions
Can a consultant submit the EDGE application for my company?
The applicant’s authorised employees or staff must make submissions in the Business Grants Portal. A consultant can assist with preparation, scoping and document review. Your company should retain control of access and declarations, understand the submitted information and own the follow-up throughout delivery and claims.
Can I change suppliers after EDGE approval?
Do not treat a supplier change as an ordinary project amendment. The current guidance requires termination and a fresh application before proceeding with or paying the new vendor. Obtain clarification on your circumstances before acting, because completed work or payments can affect a fresh application’s supportability.
Do I need to wait until completion to prepare claim documents?
Prepare the evidence structure at the start and collect records throughout delivery. The claim itself follows completion and full payment, subject to the activity’s timing and requirements. Keeping documents as work happens is much easier than reconstructing outputs, invoices and payment links near a deadline.
Activity requirements and approved terms apply. Illustrative examples are not funding offers.
