Quick answer: Construction company website maintenance is more than updating WordPress. It must keep approved project credentials and case studies accurate, verify downloadable capability documents, and test the entire request-for-quotation (RFQ) path through to the sales or estimating team. A site may load perfectly while still showing an outdated capability PDF, an unauthorized project photo or an enquiry form that never reaches an owner.
A prospective client wants to understand the contractor’s actual role, comparable projects, delivery scope and how to start an enquiry. The website team should not invent technical capabilities, schedules or prices. It needs an approval trail for published claims and a testable journey from a visitor’s phone to the person responsible for responding.
Could your site be losing project enquiries?
Share a capability-page URL, one project page and your enquiry form. IT Systems can identify the checks and maintenance scope.
What makes a contractor website different?
A project portfolio is sales evidence, but its inputs come from project delivery, engineering, marketing and business development. Client names, actual contractor role, scope, completion status, photographs and results need a source and permission to publish. Work-in-progress images, location details and progress claims require particular care. Stock or AI editorial imagery must never be presented as a completed customer project.
RFQs may start on a capability page, a comparable-project page or a service page. The receiving team needs to know the source, project type and next owner. If the form only requests a consultation, the confirmation message must not imply that an official quotation has been issued. Drawings, bills of quantities and other attachments can be sensitive; decide upload limits, access and retention before enabling them.
Nine recurring maintenance checks
- Capability documents: confirm the PDF version, revision date, scope and contact details against the approved master; test downloads on a phone.
- Project pages: check the permitted name, location, contractor role, work package, imagery and status with the project owner.
- Service scope: remove claims of full general-contracting responsibility if the firm only delivered a specialist package.
- RFQ form: test mandatory fields, project category, location, indicative timing and post-submit feedback; collect only information needed at this stage.
- Attachments: test file types and size limits, access controls, malicious-file safeguards and failed-upload recording.
- Routing: verify enquiries reach the right sales or estimating owner and a backup owner when someone is unavailable.
- Call and messaging actions: open them on a phone, check the current contact details and make sure overlays do not cover them.
- Discovery: confirm key project pages remain indexable, canonicals and internal links are correct, and changed URLs do not strand visitors on a 404.
- Technical care: maintain recoverable backups, controlled plugin/theme updates, security monitoring and a form retest after changes.
Test an RFQ from a phone to the estimator
Choose a public service or project page and agree a clearly marked TEST enquiry with the sales or estimating team. Open the page on a logged-out phone, find the CTA, test the call action and submit sample contact and project details. If uploads are enabled, use a harmless approved test file, never a client’s real drawing. Record the source URL, time, device, on-screen response and any request ID.
The receiving owner should confirm that the same enquiry appears in email or CRM, that the attachment can be opened and that responsibility for the next response is clear. Also test a missing phone number, an oversized or prohibited file, duplicate submission and delivery failure. A “success” notice in the browser is only half of the test; verify receipt at the other end. Mark or remove TEST records after reconciliation.
How should an inaccurate project claim be corrected?
Identify the public URL, visible version, revision date and approved source. If an image or project detail was not authorized, have the responsible business owner decide whether it must be hidden immediately. Then update the CMS source, downloadable PDF and related images; clear the relevant cache and re-open the page while logged out. Record the affected pages, approver, correction time and after-fix evidence.
Do not change a paragraph while the capability PDF, project card and social post still disagree. Never make up floor area, contract value, certifications or customer references. When a URL changes, check internal links and redirects so both visitors and search engines can still find the material.
Who owns which decision?
| Issue | Business owner | Website team |
|---|---|---|
| Incorrect project details | Project lead approves the facts | Update CMS, PDF, cache and links |
| Missing RFQ | Sales confirms owner and priority | Check form records, email, CRM and reproduce |
| Upload fails | Sales defines required files | Check limits, security and access |
| Site outage or compromise | Site owner sets business priority | Contain, restore, retest and report |
Data handling and scope boundaries
An RFQ may contain names, phone numbers, locations, drawings and preliminary budgets. Restrict access, avoid publicly guessable file URLs, and define storage and deletion in the company’s process. Backing up WordPress does not mean the CRM, mailbox or external document repository has also been backed up. Each system needs an owner and its own restore test.
Routine maintenance can cover approved content updates, links, software updates, backups and lead delivery checks. A contractor portal, automated cost estimator, ERP/CRM integration, complex document permissions or a complete portfolio redesign is a separate project requiring specifications and acceptance criteria. The website-management pricing page is a reference; the final scope depends on page volume, integrations and incident coverage.
What should management see in a maintenance report?
Report which project or capability pages changed and who approved them; broken PDF or link fixes; end-to-end TEST outcomes; form and attachment incidents, detection time and receiving owner; backup, update and security status; and items still awaiting business approval. Separate CTA clicks from RFQs actually received and from qualified opportunities confirmed by sales. A click is not a verified lead.
Frequently asked questions
How often should we test the RFQ form?
Test after changes to the form, plugins, email or CRM and on a cycle that matches enquiry volume. An active campaign may warrant closer monitoring. The essential step is confirmation by the receiving owner.
Should every project go in the portfolio?
No. Publish only projects, photos, client details and figures that the business is permitted to disclose. A smaller portfolio with a clear scope and evidence is more useful than a long, unverifiable list.
Should drawings be uploaded through the website?
Only when security controls, file limits, access rights and retention have been defined. Otherwise collect an initial contact request and exchange documents through a channel approved by the business.
Will IT Systems author engineering claims for the contractor?
The website team can help present, update and test approved material. The contractor remains responsible for validating technical scope, figures, imagery, certifications and capability claims.
Check enquiry delivery before launching a campaign
IT Systems can review your portfolio, downloadable documents, RFQ form and sales handoff within an agreed scope.
