Loading...
Loading...
SID application website
Your consent process often names a web address for public inspection. I publish the approved pack there, against a register you can certify. Your planning consultant supplies the wording, the dates and the period.
Three routes
Choose who controls the address and how often you repeat the work. The inventory decides whether the company site or a dedicated site is safer at this volume.
You run a corporate or project site and you control the domain. I add the application section, the notice pages and the document library under an address you own. This route is the slowest to start when another agency controls that site. That agency then controls your print deadline. The inventory also checks whether that site can hold the volume at all, before you print the address.
Scoped in writing after the inventory.
One application, one domain, live at the exact address printed in the newspaper notice and the site notices. It holds the notices, the description, the EIAR volumes, the NIS, the drawings and the later releases. It holds nothing else. Nobody else stands between you and the address, and nothing about the application can disturb your corporate site.
Scoped in writing after the inventory.
You lodge several consents across a pipeline of substations, circuits, arrays or schemes. Each new site reuses the approved structure, but receives its own inventory, its own register and its own written scope. The second application starts from an accepted structure, so the inventory takes the time, not the build.
Scoped in writing after the inventory.
Who does the work
Scope
The process
The inventory comes first. The written scope then names the publication dates your consultant supplies, the approval points and the accepted document register.
We agree the route, the domain, the sections in scope, and who signs the certification.
Output: A written scope, the domain decision, and the dates your consultant confirms.
I list every document and drawing against your lodged index. I report file counts, file sizes, duplicates, and files that do not open.
Output: A document register, the section tree, and a written list of the problem files.
I build the notice pages, the description page and the empty document sections from blocks I already own.
Output: A private preview site, with the section tree agreed at step 2.
I load the description, the notice wording, the EIAR volumes, the NIS, the drawings and the appendices.
Output: A complete preview site, and a flat index of every file with its size.
I check every listed file against the register with an automated link and render check. I open a defined sample on a phone and a laptop. Your approver reviews the preview.
Output: A reconciled register, a link and accessibility report, and your approver's sign-off.
I publish the site on the date your consultant confirms. I hand over the certification pack, the domain, the files and the site.
Output: A live site, a certification pack ready for signature, a recorded take-down date, and an archive copy.
Safeguards
4 things go wrong on an application site. The address does not resolve. The site and the lodged pack drift apart. A file will not open. The site disappears too early.
Questions
No. This would be the first, and the relevant work is 3 jobs. I replaced a PDF-only report process with a headless CMS for an enterprise building-materials group. I shipped an accessible public-sector site on Next.js and Sanity. I launched a small Next.js site inside a week. Everything on this page describes the job, not a delivered one.
We sign a confidentiality agreement before you send anything. The pack sits on storage named in the written scope. I close the preview to search engines and to anybody without the link. Nothing goes public before the date your consultant confirms. I delete every copy I hold at handover.
Your planning consultant does. I publish their approved wording word for word and change nothing. They also confirm the publication period and the take-down date, and the written scope uses the dates they give. Send the pre-application determination when you have it.
I reconcile the register file by file against your lodged index. I add a flat index page that lists every file as one direct link. I hand you a written acceptance report. The certification stays your signature, on my evidence.
The inventory comes first: file count, file sizes, duplicates, and files that will not open. The acceptance check then runs an automated link and render pass over every listed file. I open a defined sample on a phone and on a laptop before anything goes public. I flag an oversized file. I quote a split or a re-render as separate document work.
Your consultant confirms the duty. In practice it means text search across the set, and navigation per volume and per chapter. It also means a plain index that works without JavaScript. Where a source file is a scanned image, I flag it in the inventory and quote the repair separately.
The initial scope names the later releases I include. A reissue at volume, with a paired annotated and clean set, gets its own inventory. It also gets its own written scope before work starts.
Your consultant confirms the period and any extension. I record the take-down date and keep the site available for that period. Then I hand you a full archive copy of the site and every file. You decide whether it stays online.
Send the lodgement date, the newspaper date and the lodged document index. I return the publication risks, the missing decisions and a proposed scope in writing.
Send me your document index