Build Reliable Website Monitor With Change Alerts and Screenshot Evidence

I need an experienced website-monitoring and automation specialist to create a reliable application-status monitor for: https://www.local817.com/transportation GOAL Notify me promptly when applications for new drivers change from CLOSED to OPEN, with a screenshot showing the application section. I’m open to custom software or an established monitoring service. Recommend the approach that offers the best reliability, maintainability, and reasonable ongoing costs. EXISTING RESOURCES I have an existing Python monitor, source code, and a Hostinger KVM 1 VPS running Ubuntu 24.04. These are available but OPTIONAL. You may improve the existing system or recommend a different solution. Explain your recommendation before implementation. REQUIRED BEHAVIOR • Monitor the actual application-status heading. Conditional instructions containing “OPEN” elsewhere must not trigger a false opening alert. • Aim for checks approximately once per minute, subject to website restrictions and loading time. State realistic detection delays and limitations. • Send an opening alert promptly after detection, independently of routine health messages. • Clearly distinguish OPEN, CLOSED, uncertain/unrecognized content, and failed checks. • Notify me about meaningful changes to the application section, without excessive alerts for unrelated page changes. • Retry temporary failures and report persistent monitoring problems. • Notify me when monitoring recovers. SCREENSHOT EVIDENCE • Attach a screenshot showing the application-status heading when OPEN is detected. • Use the same page load for detection and screenshot evidence whenever technically possible. • Include the website link, previous and detected statuses, and timestamp in America/New_York time, automatically adjusting for daylight saving. • Capture available evidence for unexpected changes and label those alerts “Needs manual review.” • If screenshot capture fails, send the status alert promptly anyway and explain that the screenshot is unavailable. • Retain screenshots and relevant page content for troubleshooting, with an agreed retention period. NOTIFICATIONS Telegram is optional. Recommend suitable methods such as push notifications, SMS, email, or Telegram. Quote a primary method and optional backup, including all recurring costs. Explain notification retries and what delivery confirmation is available. RELIABILITY AND ACCESS • Operate continuously without my phone or computer staying on. • Recover automatically from service interruptions. • Include independent outage detection so I know if the monitor itself stops working. • Provide access to timestamped check history, detected status, errors, and notification results. • Protect credentials and provide secure administration. • Disclose all hosting, subscriptions, paid services, and third-party dependencies. • Keep necessary accounts under my control. ACCEPTANCE TESTING Demonstrate the complete detection-to-alert process using controlled test pages or fixtures: 1. CLOSED → OPEN sends the correct alert and screenshot. 2. Conditional wording containing “OPEN” does not create a false alert. 3. Unexpected application-section content produces a manual-review alert. 4. Website failures, screenshot failures, and notification failures are handled correctly. 5. Monitoring recovers after an interruption. 6. A complete monitor outage is detected independently. 7. Measured detection and notification delays meet agreed targets. A “send test message” button alone is insufficient. Do not modify the real Local 817 website. Clearly label test alerts and restore live monitoring afterward. Include a live observation period before final acceptance. FUTURE EXPANSION — QUOTE SEPARATELY If successful, I plan to add Teamsters Local 728 and Local 399. Allow for separate monitoring rules and clearly labeled alerts. Verify the appropriate official source for each before quoting; phone-recording monitoring, if needed, would be a separate scope. Applications may remain closed for months or longer. Explain long-term operating costs and maintenance needs. HANDOVER AND SUPPORT For custom software, provide complete source code, dependencies, and deployment, backup, and recovery instructions. For an established service, provide account ownership, configuration documentation, export options, and any limitations or vendor dependencies. Document the solution so another qualified professional can maintain it. Specify the included bug-fix/support period, exclusions, ongoing support rates, and expected response times. I may need paid troubleshooting or upgrades years later, so explain your support options without promising indefinite availability. PRICING I prefer fixed-price milestones: 1. Assessment and written recommendation. 2. Implementation and deployment/configuration. 3. Acceptance testing, observation period, and complete handover. Quote future additions and ongoing maintenance separately. Additional charges or scope changes must be agreed before work proceeds. PLEASE INCLUDE IN YOUR PROPOSAL • Examples of similar monitors you have built or configured. • Your recommended approach and why it fits this website. • Realistic detection delays and known limitations. • Screenshot and notification capabilities. • Assessment price, implementation estimate, timeline, and all recurring costs. • Warranty and long-term support options. Please communicate in plain language and provide evidence of completed tests.